cancel
Showing results for 
Search instead for 
Did you mean: 

Create Shadow database schema (SYB) failed

Former Member
0 Kudos

Hi,

We are doing SOLMAN upgrade from 7.1 SP14 to 7.2 SP03. While performing this activity under PRE-PROCESSING stage for JAVA stack, we are getting following error message , however ABAP has already reached LOCK_EU phase :

Error in Create the shadow database schema (SYB) Step ::

com.sybase.jdbc3.jdbc.SybSQLException: Attempt to locate entry in sysdatabases for database 'mas' by name failed - no entry found under that name. Make sure that name is entered properly.

Attempt to locate entry in sysdatabases for database 'mas' by name failed - no entry found under that name. Make sure that name is entered properly.

The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Error while executing Task with input file ExecuteTasks_SYB.xml and task CREATE_SHADOW_SCHEMA_SYB.

Cannot configure shadow schema; for more information

Could not execute 'E:\SOL_UPG_SP03\SUM\jvm\jre\bin\java.exe -cp D:/usr/sap/SKD/DVEBMGS01/exe/sybjdbc/jconn3.jar;E:\SOL_UPG_SP03\SUM\sdt\lib/sdt_db_SYB.jar;. com.sap.sdt.db.tools.syb.SQLMain D:/usr/sap/SKD/DVEBMGS01/exe/sybjdbc/jconn3.jar jdbc:sybase:Tds:<DB_HOST>:4901/SKD?ENABLE_FUNCTIONALITY_GROUP=1 sapsso ', return code '200'. Check if process output file(s) 'E:\SOL_UPG_SP03\SUM\sdt\log\SUM/CREATE_SHADOW_SCHEMA_SYBTaskExecutorService.OUT', 'E:\SOL_UPG_SP03\SUM\sdt\log\SUM/CREATE_SHADOW_SCHEMA_SYBTaskExecutorService.ERR' have been created.

System Details :

SID: SKD

DB: ASE 16.0 (in Linux) & CI is in windows 2008 R2 SP01

https://wiki.scn.sap.com/wiki/display/SYBASE/ASEError911 holds similar issue details. But with similar hardware we had done test upgrade.

Regrds,

Nilutpal

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi ,

Issue was with SUM synchronization issue in between ABAP & JAVA stacks. We had created AGS ticket for it . They have made some changes under SUM directory file AND WE HAVE PROCEED FURTHER. However same issue didn't come in next system . As per AGS response this issue comes if any malfunction happens in ABAP & JAVA upgrade synchronization. If you reset SUM also, this problem will be solved .

Regards,

Nilutpal.

Answers (0)