Additional Blogs by Members
Showing results for 
Search instead for 
Did you mean: 
Former Member
0 Kudos

After migrating a system to DB2, DB connection should be set to DB2 database automatically. But after migrating PI system on DB2 database; I was unable to run DBACockpit.

Below are the error which I was getting..

SQL Execution error:

"SAPR3.GV$INSTANCE" is an undefined name. SQLSTATE=42704


Error in "CL_DB6_TREE_NAVIGATOR===============CP CL_DB6_TREE_NAVIGATOR=======CMD12" with return code system not reached

could not start with system PPI

check the system registration.

  There was another problem when I migrated ECC system to DB2 database. The migrated system was still showing older DBsystem under DBACockpit.


If you come across this kind of situation, it might be the problem of database connection or user defined function library path is not defined properly.

There are three options to solve this, I followed option 3 and had solved the problem.

Option 1:

1. Call the DBACockpit
2. In the navigation frame, choose Configuration -->Monitoring settings.
3. Choose UDF Configuration

The DBA Cockpit assumes that this path is the path to the executable of the SAP system as it was created during the standard migration procedure. Check if the path is correct.

Option 2:

Also try to create DB connection (click on Database connection-->ADD).

Option 3:

1. Call the DBACockpit

2. Click on the refresh (Database) button

Refresh (database) button

3. Restart the instance.