Post PDB creation task failing with ERRORMSG: Failed to stop CDB listener.

[baig]

Hi,

hope you are doing good. I was upgrading from 12c to 19c.
During the post pdb creation tasks while running the below command i encountered the following error.


source DATABASE SID = JVJ

19C CDB SID = TEST

perl $ORACLE_HOME/appsutil/bin/txkPostPDBCreationTasks.pl -dboraclehome=/p05/orajvj/app/tech_st/19.3.0/dbhome -outdir=/p05/orajvj/app/tech_st/19.3.0/dbhome/appsutil/log -cdbsid=TEST -pdbsid=JVJ -appsuser=apps -dbport=1581 -servicetype=onpremise

*******FATAL ERROR*******
PROGRAM : (/p05/orajvj/app/tech_st/19.3.0/dbhome/appsutil/bin/txkPostPDBCreationTasks.pl)
TIME    : Tue Feb  9 08:39:11 2021
FUNCTION: main::stopPDBListener [ Level 1 ]
ERRORMSG: Failed to stop CDB listener.


the message in the log files is as below.

TNS-01150: The address of the specified listener name is incorrect
 NL-00303: syntax error in NV string

Please advise.

Thanks in advance for your usual support.

[baig]

Hi,

I didnt choose the option to create a listener during dbca. Also i have checked the listener and tnsnames.ora in the 19c oracle home, here the port number is 1521.

but the original port for source db is 1581.

Thanks

[ErmanArslansOracleBlog]

Check this note -> Execution of txkPostPDBCreationTasks.pl failed with Error Failed to stop CDB listener (Doc ID 2510727.1)

[baig]

Hi,

I checked the referred document. is it applicable to non RAC db as well?

I killed the listener and ran the process again it is not able to connect to apps schema. please check the attached log file.cannot_connect_apps_schema.txt

the log file says

ERROR:
ORA-12541: TNS:no listener


Warning: You are no longer connected to ORACLE.

[ErmanArslansOracleBlog]

It is appliacable to non-RAC DB only.

"Bounce listener only if it is non-RAC and service type is not DBSYSTEM"

[baig]

Hi,

I followed the document and still i see the apps schema connection error.
Thanks

Check this note -> Execution of txkPostPDBCreationTasks.pl failed with Error Failed to stop CDB listener (Doc ID 2510727.1)

[ErmanArslansOracleBlog]

It makes you comment the relevant lines.. Basically, It disables bouncing listener in non-RAC systems.

  # stopCDBListener();
  # sleep 15;

[ErmanArslansOracleBlog]

Go to your initial state, and retest.

[baig]

Hi,

I started as suggested.

Pattern found...
================
EXIT STATUS: 1
Invalid APPS database user credentials.
LOG FILE: /p05/orajvj/app/tech_st/19.3.0/dbhome/appsutil/log/TXK_POST_PDB_Tue_Feb_9_12_31_51_2021/validate_apps_password.log.
*******FATAL ERROR*******
PROGRAM : (/p05/orajvj/app/tech_st/19.3.0/dbhome/appsutil/bin/txkPostPDBCreationTasks.pl)
TIME    : Tue Feb  9 12:39:04 2021
FUNCTION: main::validateAppsSchemaCredentials [ Level 1 ]
ERRORMSG: Invalid APPS database user credentials.
*******FATAL ERROR*******
PROGRAM : (/p05/orajvj/app/tech_st/19.3.0/dbhome/appsutil/bin/txkPostPDBCreationTasks.pl)
TIME    : Tue Feb  9 12:39:04 2021
FUNCTION: main::validateAppsSchemaCredentials [ Level 1 ]
ERRORMSG: Invalid APPS database user credentials.

[ErmanArslansOracleBlog]

So, we fixed the listener related error..

The new error is related with the apps connection..

This error is already documented. Fix is as follows;

Database parameter instance_name was set to PDB_NAME . It should set to CDB_NAME

Reference: 19c Database with Oracle E-Business Suite R12 Known Issues & Solutions (Doc ID 2662860.1)

[baig]

Hi

thanks for the updates.

I followed the document from one of your blogs already.

"database parameter instance_name was set to PDB_NAME . It should set to CDB_NAME."

it is set to CDB_NAME only.

cdb name : TEST
pdb name : JVJ

SQL> show parameter instance;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
active_instance_count                integer
cluster_database_instances           integer     1
instance_abort_delay_time            integer     0
instance_groups                      string
instance_mode                        string      READ-WRITE
instance_name                        string      TEST

please advise.

[baig]

Hi,

hope you are doing good. are the below instance settings appropriate?

please update.

thanks

[ErmanArslansOracleBlog]

What do you have in the log file named -> "/p05/orajvj/app/tech_st/19.3.0/dbhome/appsutil/log/TXK_POST_PDB_Tue_Feb_9_12_31_51_2021/validate_apps_password.log" ?

exception says invalid apps password. So either txkPostPDBCreationTasks.pl connects to wrong database (CDB-PDB) related or it uses a wrong apps password. Do your checks accordingly..

[ErmanArslansOracleBlog]

Note that;
The connection string format used by txkPostPDBCreationTasks.pl is as follows;

$GLOBAL_CONFIG->{$APPSUSER_KEY} . '/' . $GLOBAL_CONFIG->{'appspass'} . '@' . $GLOBAL_CONFIG->{$PDB_SID_KEY};

It uses sqlplus to execute sql in EBS database.

"Invalid APPS database user credentials" exception is thrown during the connection...

 txkPostPDBCreationTasks.pl does the following (and that exception is thrown in your case..);

sqlplus /nolog
SQL>connect /as sysdba
SQL>connect apps/<apps_password>@<PDB_SID_KEY>

So you can test that type of connection on your own using sqlplus .. this may give you some idea to fix the problem.

[baig]

Hi,

Thanks a lot for the updates.

The log file

"/p05/orajvj/app/tech_st/19.3.0/dbhome/appsutil/log/TXK_POST_PDB_Tue_Feb_9_12_31_51_2021/validate_apps_password.log"

ERROR:
ORA-12541: TNS:no listener


Warning: You are no longer connected to ORACLE.

and when i try to connect as suggested. i see the below error.

SQL> connect /as sysdba
Connected.
SQL> connect apps/myapp1213@TEST
ERROR:
ORA-01017: invalid username/password; logon denied

Thanks

[ErmanArslansOracleBlog]

You have no listener error in that log.. So please take the corrective action.

Also you get invalid password when you try the login using sqlplus.. Take the corrective actions there as well.

I already send you the reasons behind.. The errors are obvious. The reasons are clear. So it is your task to throubleshoot your environment, and take corrective action baig. You have the connection to the environment, so you can solve these errors and then rerun the script.