This chapter contains information about the following:
Common system administration problems
Frequently-asked general questions
Common Oracle WebLogic server questions
Common API questions
Cannot Log On or Access Certain Functionality
If users cannot log on, check these possibilities:
You may need to specify a different Oracle WebLogic server port or server name.
You may need to correct the database instance entry in the Tnsnames.ora file.
Make sure the Oracle Communications MetaSolv Solution (MSS) Application is deployed on the Oracle Application Server.
Make sure users are added to the third party security server.
Make sure users have been added to the MetaSolv Solution.
Make sure the MetaSolv Solution database resources have been deployed.
If the system seems slow, check these possibilities:
Verify the Custom Attribute Refresh period in Gateway.ini [CA] section.
Make sure MEM_ARGS in startMSLVServer followed the recommended setup guidelines.
For example, for a machine with 2GB physical memory:
Xms size = 2048MB * 0.375 = 768m NewSize = 768m / 3 = 256m MEM_ARGS="-Xms768m -Xmx768m -XX:NewSize=256m -XX:MaxNewSize=256m"
Make sure garbage collection verbose mode (-verbosegc) is not turned on.
Turn off unnecessary logging for the Oracle WebLogic server using the Administration Console.
Turn off unnecessary logging in loggingconfig.xml.
Make sure Server Name > Configuration > File > Reload Period is set to -1.
Check the amount of memory being used.
Check the CPU and disk usage on the machine hosting the MetaSolv Solution database.
Check the database connections.
Check the execute queue.
Make sure the Native IO is enabled to improve performance. See "Why Do I Have a Core Dump in My Domain Directory?" for special instructions.
Run the mdl_cmp.sql script to help maintain the database structure for primary and foreign keys, indexes, and sequences.
Run database statistics.
The Oracle WebLogic Server Does Not Start
If the Oracle WebLogic server will not start up, try the following:
Start the Admin Server using the startMSLVadmin script in the domain directory.
Start the Oracle WebLogic Application server.
Run the startweblogic.cmd from a cmd prompt. If the Oracle WebLogic license has expired, you will see messages in the Oracle console. If you see messages about an expired or invalid license, you should contact Oracle Global Customer Support.
If you have a valid license and Oracle WebLogic server will not start up, replace the config.xml file in the domain directory with the config.xml.booted file. The config.xml.booted file represents the contents of the config.xml file the last time that Oracle WebLogic server was successfully started. Oracle WebLogic server should successfully start with this file. If it does, you may want to compare its contents with the contents of the config.xml used in the unsuccessful startup. The difference in the two files is the cause of the startup failure.
You must be sure that the database configured in the JDBC URL of the connection pools is the same database identified as in the tnsnames.ora file found in the Oracle Thin Client installation folder.
A Link on the Start Page is Not Working
If a blank window with a logo appears, check the following:
Are the browser settings correct? See MetaSolv Solution Installation Guide for instructions.
Is the parameter granting access to the EXE set to true in the Zac_config.xml file? See MetaSolv Solution Installation Guide for details.
Find out if an error message appeared during the download. If there was a message, ask the user to send you a copy of the ZAC.log file in the MetaSolv Solution desktop Config folder. This log file will contain copies of any download error messages.
I Cannot Access the Administration Console
Check to see whether the Admin server is running. It must be running to allow access to the Administration Console or to perform any administrative function.
A Job Sent to the Background Processor Did Not Complete
If jobs sent to the background fail, look for the following the types of problems:
End-user errors
Missing files
Missing database profiles
System problems
End users must resolve errors they create in their jobs. Review the error messages that occur in the Job Queue and determine whether or not an error was caused by user input. Check the online Help for assistance with managing the Job Queue or see "Running Background Processor" for more information.
Files that MetaSolv Solution Expects to Find are Missing
MetaSolv Solution expects to find files where they were installed, but they may have been moved or removed altogether, perhaps as the result of reconfiguration efforts.
If files no longer exist or are suspected of having become corrupted or virus-infected, uninstall and then reinstall MetaSolv Solution or contact Oracle Global Customer Support for assistance. For guidance about reinstalling, see MetaSolv Solution Installation Guide.
Connections to a Database are Failing
If a log file contains messages that indicate a failure to connect to the MetaSolv Solution database, check the tbs_util.ini, lerg.ini or npasplit.ini file to be sure it contains a profile for the database in question.
Java must be installed and you must have access to the logviewer.cmd or logviewer.sh on your machine. Located in MSLV_Home/server_name/appserver/bin directory.
Many Errors are Being Logged for the Background Processor
Rarely, the Background Processor can contain a long list of errors for jobs that did not complete or that completed with errors. Pause the queue to allow executing jobs to complete and, if feasible for your business, clear the queue and reboot. This sets the job statuses to Delete in the database.
If necessary, the database administrator can access the Oracle database and reset a job status to Ready so it can run again, but MetaSolv does not recommend depending on that ability.
Graphics are Not Displayed in the GUI
Check to be sure that the MetaSolv Solution folder on the client contains the TBSGraphicLoad.exe file. This file preloads tables with graphic images. Running this file is a manual step that is included in the instructions in the MetaSolv Solution Installation Guide. Although the .exe file is loaded to all workstations as part of the client installs, it only has to be run from one workstation once against the database to work for everyone.
Can I Combine My Oracle WebLogic Directory with the MSLV Directory?
You should not combine the MetaSolv Solution directory with other directories, although the product will work if you do. Upgrades target specific directories and will not be applied if you move the files in the MSLV directory.
How Do I Enable All of the Links On the Start Page?
Set the parameters for those products to True in the Zac_config.xml file on the Oracle WebLogic server. See MetaSolv Solution Installation Guide for details.
How Do I Find Out the Names of the JAR files?
Display the Runtime page according to directions in "Getting Oracle WebLogic Server Runtime Information".
Yes. For instructions about uninstalling the product, see MetaSolv Solution Installation Guide.
What Do I Do if I See an Error in the Console Log?
If you see an error in the console log (/appserver/logs/mslv01.mss.log), run the Log File Viewer to review more detailed logging information that has been written to appserverlog*.xml files. WebLogic-generated log errors can be viewed from the Administration Console at Servers > servername > General >. Click the link for View server log at the bottom of the page.
What Do I Need to Check to Be Sure All Passwords Match?
If you change the password for the APP_MSLV user in the Oracle database, you must change it in the Administration Console for both connection pools. At JDBC > Connection Pools > MSLVPool >General >, click Change next to Password > Enter new password. Repeat for MSLVDbTracePool.
If you change the password for the APP_API user in the Oracle database, you must change the password in the [Session] section of /appserver/gateway/gateway.ini.
[Session] User=app_api Password=*******
Note:
You must encrypt this password in the gateway.ini file using MetaSolv Solution utilities. See "Copying Encrypted Passwords to Gateway.ini" for more information.If you change the password for the administration user for the WebLogic Administration Console, you must also change it in /appserver/gateway.ini:
[JNDI] User=administrator Password=******* Factory=weblogic.jndi.WLInitialContextFactory URL=http://localhost:9001
Note:
You must encrypt this password in the gateway.ini file using MetaSolv Solution utilities. See "Copying Encrypted Passwords to Gateway.ini" for more information.What are the Default Passwords?
The default passwords for APP_API and APP_MSLV are set by the System Administrator during the database installation process.
When Does Disregard-Logging Start?
The following messages appear in the console log at server startup. Logging will initialize when the server is completely started.
log4j:WARN No appenders could be found for logger (org.apache.struts.util.PropertyMessageResources). log4j:WARN Please initialize the log4j system properly.
What Happens if I Change the HTTP Port for a Server Process?
If you change the HTTP port for the server process (using the Oracle WebLogic domain wizard) without reinstalling MetaSolv Solution, you must also change it in the following places:
A start script for the server process, for example /mslvdomain/startMSLV01.sh
/appserver/Gateway.ini:
[JNDI] User=administrator Password=******* Factory=weblogic.jndi.WLInitialContextFactory URL=http://localhost:9001
Affected ini files in /appserver/config - these must be distributed to client machines manually or using ZAC. See "Using the Zero Admin Client (ZAC) to Deliver Changes" for more information.
Why Do I Have a Core Dump in My Domain Directory?
This problem is caused by turning on Use Native IO using the WebLogic Admin Console. If it is disabled, it will not generate a core file. MetaSolv recommends that the Native IO be enabled to improve performance.
To work around this problem, delete the core dump file in domain directory before server restart; otherwise it will grow and fill up the file system. You should wait for the core dump to complete after shutdown before trying to restart.
See the Oracle WebLogic Server documentation for more information.
How Do I Know Which Database My Oracle WebLogic Server is Connected To?
Display the Runtime page according to directions in "Getting Oracle WebLogic Server Runtime Information".
How Do I Know When to Restart the Server or the Database?
For a Gateway.ini change, restarting the Oracle WebLogic server is required.
In the Oracle Administration Console, any parameter that requires a restart after changing it has a yellow warning icon next to it. The warning icon pops up when you click the parameter.
The icon indicates that changes to this attribute may require the restart of one or more servers. If you alter the value of this attribute, running servers will not reflect the change until they are restarted, and so you may need to restart multiple servers for the new value to take effect.
After a custom portlet is added into the registry, you must restart the Oracle WebLogic server or redeploy the application (nur.ear) in order to reload the portlet registry.
Certain key Oracle database initialization parameters require the Oracle database to be shut down and restarted. Refer to the Oracle database documentation for assistance.
Can I Redirect an Existing Oracle WebLogic Server to Another Database?
To redirect an existing Oracle WebLogic server to another database:
The connection pool configurations in the Administration Console (jdbc url, db user, password).
Tnsnames.ora - the mslvappserver alias to database.
Reset passwords for APP_MSLV, APP_API and APP_INT (for XML installations), if necessary.
How Can I Tell the Version of My Oracle WebLogic Server?
Display the Runtime page according to directions in "Getting Oracle WebLogic Server Runtime Information".
How Can I Force the Oracle WebLogic Server to Run as a UNIX Background Process and What are the Differences When Running This Way?
The Oracle WebLogic server runs in background if you use the MetaSolv Solution start scripts. The console log messages go to the *.mss.log file in /appserver/logs.
I Cannot Produce All of My Reports After Installing the New Release. What Should I Do?
Custom reports must be manually carried forward from one release to the next. Read "Retaining Customized Reports After an Upgrade" for instructions.
How Can I Customize My Oracle WebLogic Server Startup Script?
Edit the scripts provided by Oracle or create your own. The startMSLV* scripts are found in the domain directory. The settings in startMSLVserver script are very important and must be configured properly for the Oracle WebLogic server to start and run successfully.
How Can I Uninstall My Oracle WebLogic Server?
Undeploy the nur.ear file from the Oracle WebLogic Administration console. Delete the /metasolv directory. This will not uninstall Oracle WebLogic server. Run the Oracle WebLogic server uninstall if you want to uninstall the WebLogic software.
Which Environment Variables are Used By My Oracle WebLogic Server?
ORACLE_HOME, BEA_HOME, JAVA_HOME, JACORB_HOME, TNS_ADMIN, CLASSPATH, PATH (others are set inside the start scripts and are effective only for that process).
How Can I Look at the Objects and Object Versions Deployed to My Oracle WebLogic Server?
Display the Oracle WebLogic Administration Console or the MetaSolv Solution Runtime Info page.
How Can I Manage the Max Number of Client Connections, Threads and Other Performance Settings?
See the deployment information in the MetaSolv Solution Planning Guide or the Oracle WebLogic documentation. The answer to these questions is specific to the environment, and to what you are trying to do in the application.
How Can I Control the Default Timeout Settings?
Use the Oracle WebLogic Administration Console.
How Can I Allocate More JVM Memory to My Oracle WebLogic Server?
Increase the memory arguments being used when the app server starts. See /domaindir/startMSLVserver_name.sh or startMSLVserver_name.cmd.
What Do I Do if Users Must Access the Oracle WebLogic Server from Outside a Firewall?
You must open the http port to the Oracle WebLogic server.
How Can I Install RSA and DSA Certificates in Order to Implement SSL on My Oracle WebLogic Server?
See the Oracle WebLogic documentation for instructions.
How Can I Debug Oracle WebLogic Server Performance Problems?
See the performance information in the MetaSolv Solution Installation Guide. See the Oracle WebLogic documentation Web site. As a rule of thumb, make changes in small increments; change only one thing at a time and evaluate the effects of the change on performance.
How Do I Start the jacORB Name Service?
It is started by the startMSLVorb script.
How Can I Control Where My IOR Files are Written?
Use the IORPATH= parameter in the gateway.ini file.
ADMIN OPTION Not Granted for WOTSTWTWWOO Role After Database Upgrade
If you upgrade your Oracle Database software to 11.2.0.4, and then try to create a new user through the Security Users and Groups window in the MSS application, the following error message is displayed:
Grant role error. Please contact your system administrator. ORA-01932: ADMIN option not granted for role 'WOTSTWTWWOO'
To resolve this issue, do the following:
Note:
Oracle recommends that you perform this procedure in a test environment with a copy of your production data before implementing this procedure in your production environment.In the server parameter file (SPFILE), set the Oracle hidden parameter _grant_secure_role to True.
Restart the database.
Run the 21125221.sql file located in the installation_directory/prodfixsql directory, where installation_directory is the directory on your database server where you extracted the contents of the MSS.R6_2_1.bxxx_DBInstall.zip file; xxx is the build number.
The 21125221.sql file grants the GRANT ANY ROLE system privilege to ADMIN_ROLE with the ADMIN OPTION.