cancel
Showing results for 
Search instead for 
Did you mean: 

Source System is already used in different Configuration

0 Kudos

New game new problem .....

SLT on 7.02 with DIMS/SP5 / HANA with SP3/22

When i create SAP system in the /nltr transaction, then it works in a first time withot any problems..

But, when i delete the configuration on SLT and in HANA and create a new SAP connection to the SAME SAP system

ERROR==> Source System is already used in different Configuration

The SLT ist not start monitoring job and DTR Jobs. The DUAL tabel is missing in a first step (i create a new table) and in the second step the RS_ORDER is missing .... no tables are visible in HANA from this R3 system

Question:

How can i delete this "old" entry from my first connection?

BR, peter

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Add new SLT syste;

TA:/nSM21

Grp N Text

BY 2 Database error 100 at CON

BY 0 >

BY 1 Database error 100

BY 2 Database error 100 at CON

BY 0 >

BY 1 Database error 100

BY 2 Database error 100 at CON

BY 0 >

BY 1 Database error 100

In the work process:

C Now I'm connected to HDB

C 01: tss120-HA3/03, since=20111212223833, ABAP= CL_SQL_CONNECTION=============CP (351)

B Connection 2 opened (DBSL handle 1)

C Disconnecting from connection 1 ...

C Now I'm disconnected from HDB

B Disconnected from connection 2, con_da=

B Connect to 068:R:C as SYSTEM with tss120.cubeserv.local:30315

C Try to connect as SYSTEM/<pwd>@tss120.cubeserv.local:30315 on connection 1 ...

C Attach to NewDB : 1.00.22.356401

C Database release is NewDB 1.00.22.356401

C INFO : Database 'HA3/03' instance is running on 'tss120'

C INFO : Connect to DB as 'SYSTEM'

C DB max. input host variables : 8192

C DB max. statement length : 1048576

C DB max. array size : 100000

C DBSL FDA operation type = REMOTE

C DBSL multi tenancy enabled = FALSE

C use decimal precision as length

C ABAPVARCHARMODE is NOT active

C INFO : DBSL buffer size = 1048576

C Command info enabled

C Now I'm connected to HDB

C 01: tss120-HA3/03, since=20111212223833, ABAP= CL_SQL_CONNECTION=============CP (351)

B Connection 2 opened (DBSL handle 1)

C Disconnecting from connection 1 ...

C Now I'm disconnected from HDB

B Disconnected from connection 2, con_da=

B Connect to 068:R:R as CUBESERV_T33 with tss120.cubeserv.local:30315

C Try to connect as CUBESERV_T33/<pwd>@tss120.cubeserv.local:30315 on connection 1 ...

C Attach to NewDB : 1.00.22.356401

C Database release is NewDB 1.00.22.356401

C INFO : Database 'HA3/03' instance is running on 'tss120'

*C *** ERROR => Get session info failed : rc=259 (invalid table name: DUAL( used schemas: schemaName , defaultSchemaName CUBESERV_T33

C SELECT TOP 1 CURRENT_USER FROM DUAL;

C Disconnecting from connection 1 ...

C Now I'm disconnected from HDB

B ***LOG BY2=> sql error 259 performing CON [dbds 879]

B ***LOG BY0=> <message text not available> [dbds 879]

B ***LOG BY1=> sql error 259 [dbacds 1496]

B Connect to 068:R:R as CUBESERV_T33 with tss120.cubeserv.local:30315

C Try to connect as CUBESERV_T33/<pwd>@tss120.cubeserv.local:30315 on connection 1 ...

C Attach to NewDB : 1.00.22.356401

C Database release is NewDB 1.00.22.356401

C INFO : Database 'HA3/03' instance is running on 'tss120'

*C *** ERROR => Get session info failed : rc=259 (invalid table name: DUAL( used schemas: schemaName , defaultSchemaName CUBESERV_T33*

peter

[dbhdbsql.cpp 1131]*

lbreddemann
Active Contributor
0 Kudos

> C INFO : Database 'HA3/03' instance is running on 'tss120'

> *C *** ERROR => Get session info failed : rc=259 (invalid table name: DUAL( used schemas: schemaName , defaultSchemaName CUBESERV_T33*

Hi Peter,

the access to table DUAL is still done by the dbsl because it is still the old version.

Make sure to also update the dbsl and this error will not reoccur again.

(as a half-way workaround you could also create a public synonym for the nowadays abandoned DUAL table:

create public synonym DUAL for DUMMY;)

Anyhow, the recommended solution is to upgrade all components of the HANA system (including the HANA client software and the DBSL) when upgrading to SPS 03.

regards,

Lars

Answers (6)

Answers (6)

0 Kudos

After replacing the client library, it does not work -


> stop/start SLT system -


> create the connection is now ok

thanks for all

peter

0 Kudos

Hi

Next step:

When you have the following error in the SM21

11:41:16 DIA 017 800 STRAUBP BY 2 Database error 100 at CON

11:41:16 DIA 017 800 STRAUBP BY 0 >

11:41:16 DIA 017 800 STRAUBP BY 1 Database error 100

Then lock in the workprocess to find out what is going on:

B Tue Jan 10 11:41:15 2012

B table logging switched off for all clients

B Loading DB library '/usr/sap/T33/DVEBMGS00/exe/dbhdbslib.so' ...

B Library '/usr/sap/T33/DVEBMGS00/exe/dbhdbslib.so' loaded

B Version of '/usr/sap/T33/DVEBMGS00/exe/dbhdbslib.so' is "720.00", patchlevel (0.105)

B Connect to TMPSTRAUBP20120110104115 as SYSTEM with tss120:30315

C

C DBHDBSLIB : version 720.00, patch 0.105 (Make PL 0.105)

C HDB shared library (dbhdbslib) patchlevels (last 10)

C (0.105) close all lob locators at end of the transaction (note 1600066)

C (0.103) DBSL hint dbsl_add_stmt (note 1622681)

C (0.103) UPSERT without a primary key (note 1600066)

C (0.102) Use sys.table_columns instead of sys.columns (note 1600066)

C (0.102) Use connect property VARCHARMODE=ABAP (note 1600066)

C (0.102) Signal 11 AIX (note 1600066)

C (0.096) FAE with equi-join (note 1600066)

C (0.092) Secondary connection to HANA (note 1481256)

C (0.054) ABAP: Return technical database PPMS information (note 1419552)

C (0.053) ABAP: Return technical database PPMS information (note 1419552)

C

C

C Loading SQLDBC client runtime ...

C SQLDBC Module : /usr/sap/T33/DVEBMGS00/exe/libSQLDBCHDB.so

C SQLDBC SDK : SQLDBC.H 1.00.10 Build 0344882-1310

C SQLDBC Runtime : libSQLDBCHDB 1.00.12 Build 0351658-1510

C SQLDBC client runtime is 1.00.12.0351658

C Try to connect as SYSTEM/<pwd>@tss120:30315 on connection 1 ...

C Attach to NewDB : 1.00.22.356401

C Database release is NewDB 1.00.22.356401

C

C Tue Jan 10 11:41:16 2012

C INFO : Database 'HA3/03' instance is running on 'tss120'

C *** ERROR => Get session info failed : rc=100 (Row not found)

in my system .... wrong libSQLDBCHDB (patch 12 and on HANA patch 22)

I will now replace the library and the client software on the SLT server

0 Kudos

Hi at all

after a long "out of office" periode, i am now back in town.

My actions

1.) in SAP HANA - delete user, schema (will be deleted with user) and all associated security roles

==> done, everything is deleted

2.) in SAP HANA - delete corresponding row from table RS_REPLICATION_COMPONENTS in schema SYSREPL

==> done, there is no entry

3.) in SLT - schema in transaction LTR should not be present

==> done

4.) in SLT - stop/delete IUUC* and DTL* jobs that are released or running

==> done, there was no jobs to delete

5.) in SLT - in transaction IUUC_SYNC_MON delete Mass Transfer definition

==> done, was empty

6.) in SLT - in transaction IUUC_REMOTE check that triggers were removed

==> done, no triggers

7.) in SLT - remove corresponding entries from DBCON table (where DBMS is HDB)

==> done, there was 0 entries

8.) in SLT - check other tables like IUUC_SCHEMA_CON,IUUC_SCHEMA_RMD are empty

==> done, no entries

I look now for DBSL and actual Patch 23

peter

Former Member
0 Kudos

Hi

  How did you delete

5.) in SLT - in transaction IUUC_SYNC_MON delete Mass Transfer definition

  

8.) in SLT - check other tables like IUUC_SCHEMA_CON,IUUC_SCHEMA_RMD are empty

0 Kudos

Hello Tomas

The LTR does not delete the user and the schema. I can confirm this

Cleanup in ABAP - is done ... same problem

peter

tomas-krojzl
Active Contributor
0 Kudos

Hello,

regarding the cleanup after deleting schema in LTR (but do this on your own risk) - you need to:

1.) in SAP HANA - delete user, schema (will be deleted with user) and all associated security roles

2.) in SAP HANA - delete corresponding row from table RS_REPLICATION_COMPONENTS in schema SYSREPL

3.) in SLT - schema in transaction LTR should not be present

4.) in SLT - stop/delete IUUC* and DTL* jobs that are released or running

5.) in SLT - in transaction IUUC_SYNC_MON delete Mass Transfer definition

6.) in SLT - in transaction IUUC_REMOTE check that triggers were removed

7.) in SLT - remove corresponding entries from DBCON table (where DBMS is HDB)

8.) in SLT - check other tables like IUUC_SCHEMA_CON,IUUC_SCHEMA_RMD are empty

This is where I know SLT is recording information - however there might be more things needed - if this will not be enough we will need to run trace.

Tomas

Former Member
0 Kudos

Hey.

I have had a similar issue. When calling transaction LTR the web ui showed me an error saying Not all configurations could be loaded due to data inconsistencies The list of SLT schemas was completely empty. Even though I was also still able to schedule tables for replication in the hana studio, those tables never made it passed the "scheduled" state.

Now the problem was that I was unable to delete the schema from LTR. Additionally when I tried to create a new one with a different name I received the error Source System is already used in different Configuration.

None of the steps that Tomas suggested, solved this specific issue. After a little digging I found entries referencing my source system in the following tables:

IUUC_REPL_CONFIG, IUUC_REPL_CONPAR, IUUC_REPL_HDR

After I removed those, the error on LTR was gone and I was able to create a new SLT schema using the same source system.

I hope this helps and you have a wonderful new years.

Dominik

0 Kudos

Hi Tomas

Question:

How did you delete configuration - did you use provided webdynpro (transaction LTR)?

Answer:

Over the transaction /nltr -> WebDynpro -> Delete System -> HANA schema is after delete in LTR not deleted -> Delete user -> Schema will be deleted (automatically).

After this action i have the reported error

-


I will check the rest today

peter

Edited by: Peter Straub on Dec 14, 2011 9:20 AM

Edited by: Peter Straub on Dec 14, 2011 9:23 AM

tomas-krojzl
Active Contributor
0 Kudos

Hello,

so to ensure I understand correctly..

You failed to delete configuration via LTR (nothing changed) so you went into the HANA and deleted user and his schema directly from HANA?

Can you confirm?

If this is true - then you also need to make cleanup in ABAP - which will contain deleting content of some table, deleting Mass Transfer definition, etc.

Tomas

tomas-krojzl
Active Contributor
0 Kudos

Hello,

SP05 is introducing HUGE changes - SLT is organized completely differently...

1.) new GUI is delivered (in both SLT and in HANA) that is offering new functions - so it is preferred to use these functionas rather then doing actions manually in SLT like before

2.) All replication tables were moved from schema SYSREPL into replicated schema - except table RS_REPLICATION_COMPONENTS (in case of upgrade the tables are still there but unused)

3.) you got three new security roles created in HANA in relation to SLT - all starting with <schema name>

4.) in SLT amount of Mass Transfer IDs was reduced to just one

5.) amount of jobs was reduced - one less DTL job due to reduced MT IDs, only monitor job is executed from IUUC* jobs (no more controller jobs)

But, when i delete the configuration on SLT and in HANA and create a new SAP connection to the SAME SAP system

How did you delete configuration - did you use provided webdynpro (transaction LTR)?

ERROR==> Source System is already used in different Configuration

It seems that SLT was not removed correctly - please check (do not adjust) following:

1.) in SAP HANA - existence of replication schema

2.) in SAP HANA - content of table RS_REPLICATION_COMPONENTS in schema SYSREPL

3.) in SAP HANA - existence of user with <schema name>

4.) in SAP HANA - existence of security roles starting with <schema name>

5.) in SLT - definition of schema in transaction LTR

6.) in SLT - if IUUC* and DTL* jobs are released/running

7.) in SLT - in transaction IUUC_SYNC_MON if Mass Transfer IDs are defined

8.) in SLT - in transaction IUUC_REMOTE if triggers are defined

The DUAL tabel is missing in a first step (i create a new table)

DUAL table is removed by design - it should not be problem for SLT

How can i delete this "old" entry from my first connection?

We will work on that..

Tomas