This chapter contains basic setup maintenance and database troubleshooting information. See MetaSolv Solution System Administrator's Guide for full system maintenance information.
This section contains information about the basic maintenance tasks for Oracle Communications MetaSolv Solution (MSS).
When starting MSS, you must start components in the following order:
Database
Application server
MSS client (user workstation)
The startup scripts are located in the domain directory. The script name includes the server name. For example, if a server is named mslv01, it will have a startup script named startmslv01.sh in the domain directory.
To start MSS, run the following scripts located in the domain directory:
For Unix Linux:
startWebLogic.sh
For Windows:
startWebLogic.cmd
Starts the administration server if you are running in a domain that has a separate administration server. Start the administration server before starting the managed server(s).
For Unix Linux:
start<server>.sh
For Windows:
start<server>.cmd
Starts an application server (either managed or single) running MSS.
If you are running an administration server and a managed server on the same machine, after the managed server is started, the administration server can be shut down to release resources that the process would otherwise consume. However, the administration server must be running to allow access to the management console or to perform any administration function.
To uninstall MSS from an application server:
Start the administration server and log on to the WebLogic Server Administration Console.
To undeploy the application, do the following:
From the Domain Structure tree, click Deployments.
In the Change Center pane, click Lock & Edit.
From the Summary of Deployments pane, click the check box for nur.ear (or cluster-nur.ear).
Click Stop and select Force Stop Now.
Click Delete.
Click Yes to delete the deployment.
In the Chnage Center pane, click Activate Changes.
Repeat step 2 for each version of ASR or LSR that is installed.
To delete the data sources, do the following:
From the Domain Structure tree, expand Services, expand JDBC, and then click Data Sources.
In the Change Center pane, click Lock & Edit.
From the Summary of JDBC Data Sources pane, click the check box for each data source that is to be deleted (refer to the list below).
Services > JDBC > Data Sources > mslvDataSource
Services > JDBC > Data Sources > mslvDbTraceDataSource
Services > JDBC > Data Sources >mslvNoneTxDataSource
Services > JDBC > Data Sources >mslvProcDataSource
Services > JDBC > Data Sources >mslvWliDataSource (XML API only)
Click Delete.
Click Yes to delete the data sources.
In the Change Center pane, click Activate Changes.
In the file system on the machine, delete the MSS installation directory.
When an IP address for a server changes, adjustments must be made in the configuration. The following sections indicate how to handle this change.
The IP address or DNS name can be used to identify a machine's listen address. Oracle recommends using the DNS name.
When the IP address changes on a server's machine, you must modify the machine's IP address in the Oracle WebLogic server if it is used as the server listen address, the gateway.ini, integration.xml, tbs.ini, tbs_util.ini, and any other files that identify the server machine using the IP address.
Before the IP address changes, start the server and change the listen address to the new IP address, then implement the IP address change and restart the server.
Change the startserver.sh file to show the new address:
ADMIN_URL=http://<Admin server IP address:port number>/
If you use the DNS name of the server's host machine rather than the IP address, there is no effect when the IP address changes.
This section contains information about the causes and resolutions to common database problems so you can troubleshoot in MSS.
Problem
Listener refused the connection with the following error:
ORA-12519, TNS: no appropriate service handler found
Cause
You receive this error message when activating the data sources (DS) or when starting the server, most likely in WLI Cluster environments.
Resolution
Check the DB parameter for the number of processes. The number of processes should be high enough to hold the number of connections that you want to create in addition to the WL internal processes.
SQL*Plus may unexpectedly quit while running the upgrade under the following scenarios:
The ASAP, EBOND, EDI, JOB, and SYS user IDs do not exist on the instance.
You entered an incorrect password.
ASAP does not have DBA-level authority.
The database is not at the appropriate version level when starting the upgrade.
You do not have the standard tablespaces data and indexes.
The full directory path for the SQL script files does not include the trailing slash, you entered an invalid path, or you do not have write access to the directory.
The free space checks did not pass (minimum available tablespace free for the largest contiguous space and total free space). Check the output log (upgenv.log) for the exit reason, correct the tablespace limitation, and run the _upgmss.sql script again.
When failure occurs before the main upgrade sequence has begun (for example, during the interactive upgrade sequence), use your original selection of either upgrade mode 1 or 2 to restart the upgrade. Do not use upgrade mode 3 to restart the upgrade if a failure occurs during the interactive upgrade sequence.
If upgrade mode 1 was run more than once, all audits are lost and you must start the upgrade again from the beginning.
Check to make sure you have run the TBSGraphicLoad.exe located in the same directory as the MSS executable on the client workstation. This executable contains new and updated graphics for the MSS database. It does not need to be run by every user. It only has to run one time on the database for the release.
When _upgradetbs.sql runs, you are prompted for the directory path for the script files that are used to do the upgrade. The path must end with a trailing slash. The slash is different for UNIX/Linux and Windows:
/ for UNIX and Linux
\ for Windows
If the slash is not included, no log files are written.