Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies replies
    3
  • Answers answer
    1
  • Subscribers subscribers
    12
  • Views views
    377
  • Users 0 members are here
Related
Options

Error after upgrade PPM 23.4

Filipe Rodrigues

Hello,

I have some errors on executing the kStart.sh after finish the upgrade to PPM 23.4.

We were running PPM 2023.0.0 with Oracle on-premises, and during the upgrade we had no error, but when running kStart, these errors prevented the application from starting.

This is the list of error that we're facing when we try to update version:

"The following errors were found in the configuration of other nodes
These errors will not prevent this node starting, however it is strongly recommended to fix them
PPMUSR1 and PPMSRV1: Property com.kintana.core.server.APP_SERVER_NAMING_SERVICE_BINDING_PORT in node PPMUSR1 has the non-allowed value 1199. It conflicts with RMI_URL in node PPMSRV1"

"ERROR server:main:(ISIntegrityServerImpl.java:1675):2024/03/06-16:36:27.104 BRT: java.sql.SQLException: ORA-06592: CASE não encontrado ao executar a instrução CASE
ORA-06512: em "SPPMH_1.KNTARPT_RESCHEDULE_OUTDATED_RP", line 28
ORA-06512: em line 1"

"Caused by: Error : 6592, Position : 0, Sql = BEGIN KNTARPT_RESCHEDULE_OUTDATED_RP(); END;, OriginalSql = BEGIN KNTARPT_RESCHEDULE_OUTDATED_RP(); END;, Error Msg = ORA-06592: CASE não encontrado ao executar a instrução CASE
ORA-06512: em "SPPMH_1.KNTARPT_RESCHEDULE_OUTDATED_RP", line 28
ORA-06512: em line 1"

"ERROR server:main:(SpringApplication.java:821):2024/03/06-16:37:25.205 BRT: Application run failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.exception.FlywayValidateException: Validate failed: Migrations have failed validation
Detected failed migration to version 1.27 (alter configuration table).
Please remove any half-completed changes then run repair to fix the schema history."

"Caused by: org.flywaydb.core.api.exception.FlywayValidateException: Validate failed: Migrations have failed validation
Detected failed migration to version 1.27 (alter configuration table).
Please remove any half-completed changes then run repair to fix the schema history."

"STATUS server:main:(StreamEncoder.java:221):2024/03/06-16:37:25.210 BRT: Mar 06, 2024 4:37:25 PM org.apache.catalina.core.ContainerBase startInternal
SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[jboss.web].StandardHost[localhost].StandardContext[/pvo]]"

  • Suggested Answer

    0  

    Hi Filipe,

    You can use https://portal.microfocus.com/s/article/KM000024714 to fix the issue.

    But the real issue should be because you are using old server.xsl file, replaced by you or placed in the customization directory. Please use the OOTB file and restore any customizations in it if needed.

    Best Regards,

    Iliya

    Iliya Iliev
    PPM NSE
    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

  • 0  

    There are even more options like unsupported Oracle DB version for this PPM version, and third option where a database record may need to be updated. The last option needs a support case. But in any way you need to start with the one from the KCS article in my previous update.

    Iliya Iliev
    PPM NSE
    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

  • 0   in reply to   

    That was about the keyword "flywayInitializer'".

    This Error I had with you in the past:

    "The following errors were found in the configuration of other nodes
    These errors will not prevent this node starting, however it is strongly recommended to fix them
    PPMUSR1 and PPMSRV1: Property com.kintana.core.server.APP_SERVER_NAMING_SERVICE_BINDING_PORT in node PPMUSR1 has the non-allowed value 1199. It conflicts with RMI_URL in node PPMSRV1"

    I am not sure which one fixed the issue at that time as we worked on both:

    run kJSPCompiller.sh

    Or correcting cache.conf , the changes may be not the same in this PPM version but, there are changes about its customization also - you can check here the comments from Etienne about the new things in 23.3: Unknown error creating request - PPM User Discussions - OpenText Project and Portfolio Mgmt. (microfocus.com)

    So, you can try them again to see if they may resolve the issue again.

    Iliya Iliev
    PPM NSE
    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.