Mon. Jun 27th, 2022

Determine the exact problem.
Make a theory of a possible cause.
Test the theory to see if you see the reason.
Create an action plan to solve the problem and implement a specific solution.
Check the full functionality of the system and take preventive measures if necessary.

I’m using Oracle Database 10g Express Edition. Lately I keep running into ORA-12516 error. It says-
“java.sql.SQLException: The listener was refused connection with the following error:
ORA-12516, TNS: listener could not find an available trainer with the appropriate protocol stack
The connection handle used by the client was:
//127.0.0.1:1521/XE”

For me, the error occurs when the user does not complete with variables such as “Assertion” “Result Set” and runs multiple of them.
Sometimes I have created “Statement” or “ResultSet” developer variables in a function that I previously ownate – http://paste.ubuntu.com/7902053/ to close these variables. I didn’t close the variables in the new end block of the function they were declared with. Instead, I called this function (close_calls(..)) to close these variables and send them as parameters inside the close_calls(..) function. For example, I called the function above on lines 17 and 23 here — http://paste.ubuntu.com/7902114/

But this particular error still shows up in the control panel. close_call(…) not working? How to fix some bugs? I got advice on closing variables here — Closing database connections in Java

This chapter describes Fixit Daily to troubleshoot an Oracle Communications Unified Inventory Management (UIM) installation.

Report Problems

How can I fix my computer problem?

Run a sophisticated virus scan.
Update your software.
Reduce bloating for less money.
Check your current Wi-Fi connection.
Reinstall the working system.

  • Problems can often be resolved by closing the UIM and restarting the computer workstation it is running on. You can find a lot of information in the UIM System Administrator’s Guide.

  • If this doesn’t solve the problem, the first troubleshooting step is to check the error log of the application or process that reported the problem.

  • Prepareand collect information in advance:

  • Relevant, clear, and concise details about the problem, including when the software originated.

  • Relevant parts of these respective log files.

  • Relevant configuration files.

  • The latter are different on your system, even if you don’t normally consider them important.

  • List of all UIM components and updates installed on your system.

  • Problem: The Installer Cannot Update The KEYSTORE Application Table

    If the installer fails to update the service’s KEYSTORE table, the installer fails and displays the following error message:


    Unable to update app key store ‘AppKeyStore’. See the log files for details. For more information about performing this step manually, see the UIM documentation.

    Click the Continue button to complete the installation. Manually review the KEYSTORE application table when I say the installation is complete.

    1. Go to Oracle_Home/POMSClient.

    2. Do the followingGeneral command:


      Java_Home/bin/java -javaagent:lib/eclipselink.jar -cp POMSClient.jar yes.j2ee.poms.client.UpdateAppKeyStore DB_HostName DB_Port DB_ServiceName UIM_Schema_UserName UIM_Schema_Password go delinquent aes 128

      where:

    3. DB_HostName is the name of the database

    4. DB_Port is the database plugin number

    5. DB_ServiceName is the name of the database service and the system ID

    6. UIM_Schema_UserName is a valid schema uim database username

    7. UIM_Schema_Password is the password for the UIM schema username

    8. Connect to the KEYSTORE table of the form submission and check the following:

    9. That the COMPONENT column has a dollar value default.

    10. That the ENCRYPTALGORITHM column is aes.

    11. That the KEYLENGTH column has a value bound to 128.

    Problem: The Installer Cannot Update The Application’s INFORMATION Table

    If the installer is unable to deploy the application’s INFO table, the installer will abort and display the following error message:


    Information and facts about “ApplicationInfo” cannot be updated, just check the log filesla for more details. See the UIM documentation for more information on how to complete this step manually.

    Click the Continue button to complete the installation. Manually update the app’s INFORMATION table after installation is complete.

    1. Go to Oracle_Home/POMSClient.

    2. Run the following command:


      Java_Home/bin/java -javaagent:lib/eclipselink.jar -cp POMSClient.jar yes.j2ee.poms.client.UpdateAppInfoTable DB_HostName DB_Port DB_ServiceName UIM_Schema_UserName UIM_Schema_Password “UIM” UIM_Version SUCCESS

      where:

    3. DB_HostName is the specific hostname of the database

    4. DB_Port is the database transport number

    5. DB_ServiceName – database service destination or system identifier

    6. UIM_Schema_UserName is a great UIM database username for our own schema

    7. UIM_Schema_Password is the password for the UIM schema username

    8. UIM_Version is the UIM version to be installed

    9. Connect to the application’s INFORMATION table and verify that:

    10. Let the NAME column give you the UIM value.

    11. The VERSION column shows the correct version relative to UIM.

    12. That the STATUS column has the full value SUCCESS.

    Problem: RCU Not Working Due To Invalid Common Username Or Role Alias

    If creating an MDS schema from an RCU fails with an appropriate error message:


    ORA-65096: invalid user or role common name. Error

    This is caused by using a database ID that is not valid for regular users or roles. In addition to the normal rules for users, role names, generic usernames, and partial names must begin with C## or, preferably, C##, and be composed of ASCII characters only.

    If you are using the RCU installer (see “Creating the Database Schema (Metadata) Required for UIM”), you will usually need to provide details of the Oracle 12c (pdb) pluggable database.


    1. Make sure PDB is running.

    2. Open your own command prompt and connect to SQL*Plus.

    3. Run the following command to convert the open mode of a PDB SID from mounted to open:


      modify removable bdata bases $PDB_SID open;

    4. Run the following command to permanently switch to SID PDB:


      Edit Training Set Container = $PDB_SID

    For more information on configuring PDB, see the Oracle Database Administrator’s Guide, version 12c (12.1).