Trouble with the Cisco DCNM Database
This section includes the following topics:
Trouble with a PostgreSQL Database
Check
Table 19-5
for symptoms related to the pgAdmin III application for administering a postgreSQL database used with Cisco DCNM. For each symptom that describes your trouble, determine which possible causes apply and follow the corresponding solutions.
Table 19-5 pgAdmin III Errors
|
|
|
Error message states that the Cisco DCNM database does not exist.
|
The Cisco DCNM database name may have changed during an upgrade or reinstallation of the Cisco DCNM server software.
|
In the pgAdmin III application, perform the steps in the “Updating Cisco DCNM Database Name and Username in pgAdmin III” section.
|
Error message states that password authentication failed for the Cisco DCNM database username.
|
The Cisco DCNM database username may have changed during an upgrade or reinstallation of the Cisco DCNM server software.
|
Updating Cisco DCNM Database Name and Username in pgAdmin III
To update the Cisco DCNM database name and username in pgAdmin III, follow these steps:
Step 1 Open the pgAdmin III application.
Step 2 In the Object Browser pane, under Servers, click
PostgreSQL Database Server 8.2
.
In the right-hand pane, the Properties tab appears with several other tabs.
Step 3 On the Properties tab, double-click
Maintenance database
.
A dialog box displays a Properties tab for the server.
Step 4 If you need to change the database name, click the
Maintenance DB
field and type the correct Cisco DCNM database name.
Note The database name should be the name that you specified when you most recently upgraded or reinstalled the Cisco DCNM server software.
Step 5 If you need to change the database username, click the
Username
field and type the correct Cisco DCNM database username.
Note The database username should be the database username that you specified when you most recently upgraded or reinstalled the Cisco DCNM server software.
Step 6 Click
OK
.
Step 7 In the Object Browser pane, double-click
PostgreSQL Database Server 8.2
.
If you changed the username in Step 5, the Connect to Server dialog box appears.
Step 8 If necessary, enter the password for the username that you specified in Step 5 and click
OK
.
The pgAdmin III application connects to the Cisco DCNM database and displays the databases and login roles.
If you need additional assistance, see the Help menu in the pgAdmin III application or see the pgAdmin web site at the following URL:
http://pgadmin.org/docs/1.6/index.html
Trouble with an Oracle Database
If the Cisco DCNM server has trouble using an Oracle database, it logs the error messages in the following file:
Installation_directory
\jboss-4.2.2.GA\server\dcnm\log\server.log
Check
Table 19-6
for symptoms related using an Oracle database with Cisco DCNM. For each error message, see the possible cause and follow the corresponding solution.
Table 19-6 Cisco DCNM server.log File Errors with an Oracle Database
|
|
|
The following error appears in the server.log file:
java.sql.SQLException: ORA-01653: unable to extend table Cisco DCNMUSER.DCMRAWEVENTTABLE by 1024 in tablespace SYSTEM
|
The tablespace SYSTEM is too small.
|
Perform the steps in the “Increasing the SYSTEM Tablespace” section.
|
The following error appears in the server.log file:
[org.hibernate.util.JDBCExceptionReporter] Could not create connection; - nested throwable:
(java.sql.SQLException: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
|
The number of available sessions and processes is inadequate.
|
Perform the steps in the “Increasing the Number of Sessions and Processes” section.
|
The following error appears in the server.log file:
2009-04-08 15:53:47,125 ERROR [org.hibernate.util.JDBCExceptionReporter] ORA-00604: error occurred at recursive SQL level 1
ORA-01000: maximum open cursors exceeded
|
The number of open cursors is inadequate.
|
Perform the steps in the “Increasing the Number of Open Cursors” section.
|
Information About the Oracle SQL*Plus Command-Line Tool
The Oracle database troubleshooting procedures in this chapter require the use of the SQL*Plus command-line tool. The SQL*Plus executable is typically installed in the bin directory under the Oracle home directory. In Microsoft Windows, the default location for the SQL*Plus executable is as follows:
C:\oraclexe\app\oracle\product\10.2.0\server\bin
In Linux, the default location for the SQL*Plus binary file is as follows:
/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/bin
Linux Environment Variables
If you are using Linux, before you use the SQL*Plus command-line tool, ensure that the ORACLE_HOME and ORACLE_SID environment variables are set to correct values. For example, if you are using Oracle 10g on Linux, the following commands set the environment variables to the default Oracle home directory and SID if you are using a bash shell:
export ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server
Logging Into Oracle
Note Ensure that you know the database administrator username and password.
To log into the Oracle database by using the SQL*Plus command-line tool, follow these steps:
Step 1 Run the SQL*Plus executable.
A command prompt appears.
Step 2 Enter the
connect
command.
The Username prompt appears.
Step 3 Enter the database administrator username.
The Password prompt appears.
Step 4 Enter the password for the username that you specified.
For example, if the Oracle administrator username is system and the password is oracle, you would log in as follows:
For more information about using SQL*Plus, see the documentation for the Oracle database version that you are using.
Information About the init.ora File
The init.ora file specifies startup parameters. The default name and location of the file is platform specific, as shown in
Table 19-7
.
Table 19-7 Name and Default Location of init.ora File
|
|
|
10g
|
Microsoft Windows
|
C:\oraclexe\app\oracle\product\10.2.0\server\database\initXE.ora
|
Linux
|
/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs\initXE.ora
|
11g
|
Microsoft Windows
|
C:\app\Administrator\product\11.1.0\db_1\dbs\initORCL.ora
|
Linux
|
/usr/lib/oracle/orcl/app/oracle/product/11.1.0/db_1/dbs/initORCL.ora
|
The init.ora file should contain only one line, which is the full path of the server parameter file, as shown in
Table 19-8
.
Table 19-8 Content of init.ora File
|
|
|
10g
|
Microsoft Windows
|
SPFILE='C:\oraclexe\app\oracle\product\10.2.0\server\dbs\spfileXE.ora
|
Linux
|
SPFILE='/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfileXE.ora'
|
11g
|
Microsoft Windows
|
SPFILE='C:\oraclexe\app\oracle\product\11.1.0\server\dbs\spfileXE.ora
|
Linux
|
SPFILE='/usr/lib/oracle/orcl/app/oracle/product/11.1.0/db_1/dbs/spfileXE.ora
|
Increasing the SYSTEM Tablespace
To increase the SYSTEM tablespace, follow these steps:
Step 1 Use the SQL*Plus command-line tool to log in to the Oracle database. For more information, see the “Information About the Oracle SQL*Plus Command-Line Tool” section.
Step 2 Enter the following command:
select file_name, bytes, autoextensible, maxbytes where tablespace_name='SYSTEM';
Step 3 Enter the following command:
alter database datafile 'file_name' autoextend on next 100m maxsize 2000m;
where
file_name
is the filename from the output of the
select
command in Step 2.
The SYSTEM tablespace is increased.
Step 4 Enter the
exit
command.
Increasing the Number of Sessions and Processes
To increase the number of sessions and processes to 150, follow these steps:
Step 1 Ensure that the init.ora file exists and that it contains the single line that is applicable for your Oracle database installation. If there are additional lines, remove them.
For more information, see the “Information About the init.ora File” section.
Step 2 Stop the Cisco DCNM server. For more information, see the “Stopping the Cisco DCNM Server” section.
Step 3 Use the SQL*Plus command-line tool to log in to the Oracle database. For more information, see the “Information About the Oracle SQL*Plus Command-Line Tool” section.
Step 4 Enter the
shutdown
command. If the command fails, use the
shutdown abort
command.
Step 5 Enter the following command:
startup pfile='init_file_name';
where
init_file_name
is the init.ora filename for your Oracle database installation. For more information, see the “Information About the init.ora File” section.
Step 6 Set the number of sessions to 150 by entering the following command:
alter system set sessions = 150 scope=spfile;
Step 7 Set the number of processes to 150 by entering the following command:
alter system set processes = 150 scope=spfile;
Step 8 Enter the
shutdown
command. If the command fails, use the
shutdown abort
command.
Step 9 Enter the
startup
command.
Step 10 Verify that the number of sessions and processes is changed to 150 by entering the following command:
Step 11 Enter the
exit
command.
Step 12 Start the Cisco DCNM server. For more information, see the “Starting the Cisco DCNM Server” section.
Increasing the Number of Open Cursors
To increase the number of open cursors to 1000, follow these steps:
Step 1 Ensure that the init.ora file exists and that it contains the single line that is applicable for your Oracle database installation. If there are additional lines in the file, remove them.
For more information, see the “Information About the init.ora File” section.
Step 2 Shut down the Cisco DCNM server. For more information, see the “Stopping the Cisco DCNM Server” section.
Step 3 Use the SQL*Plus command-line tool to log in to the Oracle database. For more information, see the “Information About the Oracle SQL*Plus Command-Line Tool” section.
Step 4 Enter the
shutdown
command. If the command fails, use the
shutdown abort
command.
Step 5 Enter the following command:
startup pfile='init_file_name';
where
init_file_name
is the init.ora filename for your Oracle database installation. For more information, see the “Information About the init.ora File” section.
Step 6 Set the number of open cursors to 1000 by entering the following command:
alter system set open_cursors = 1000 scope=spfile;
Step 7 Enter the
shutdown
command. If the command fails, use the
shutdown abort
command.
Step 8 Enter the
startup
command.
Step 9 Verify that the number of open cursors is changed to 1000 by entering the following command:
show parameter open_cursors
Step 10 Enter the
exit
command.
Step 11 Start the Cisco DCNM server. For more information, see the “Starting the Cisco DCNM Server” section.