SAP Knowledge Base Article - Preview

3272559 - DB6: SQL1013N error when executing db6_update_db as postprocessing after FP update in Dual-Stack Env

Symptom

In Dual-Stack Env, when executing db6_update_db as postprocessing after FP update, SQL1013N was raised for Java stack.

In db6_update_db.log, you see:
===========
 *** script generation start at: 2022-11-16-14.35.25 ***
 Executing SQL Command :
 SQL: db2 -x "connect to <java stack dbsid>"
 OS RETURN CODE: 4
 Result: SQL1013N  The database alias name or database name "<java stack dbsid>" could not be found.  
 SQLSTATE=42705
===========

For ABAP stack, this error was not raised.

The script was executed in a normal Windows Command Line window.
The command "connect to <java stack dbsid>" in a DB2 command window (Db2 CLP) is working fine.


Read more...

Environment

SAP on IBM Db2 for Linux, UNIX, and Windows, Dual-Stack Env on Windows server

Keywords

SQL1013N, db6_update_db, Dual stack, java, FP, Windows , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.