Solved: Migration failed on data source XXX. - SAP Community

Dear colleagues,

After the installation of the patch SP15P3 on our landscape, I'm not able to migrate the datasources anymore.

Has anyone an idea?

We get the following error from console:

---------------------------------------------------

Migration

failed on data source BOFCDEV.

Failed to update schema

MAG.

---------------------------------------------------

And here are the traces generated during the migration:

---------------------------------------------------

03-02-15 11:27:45 PID=5448 THD=468 USR= MSG=0 INFO application.migration - Migrating application server

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Initializing application server, datasource="BOFCDEV", version=10.0.0

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter DbConnectionString="Provider="OraOLEDB.Oracle";Data Source="TB5";User ID="BOFCDEV";Password="****""

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ProductName=Finance

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ExternalAuthenticationConfigString=SOURCE=CtSecurity.CtBOBJAuthenticationProvider.1;CMS_NAME=v056v0;

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter InternalAuthenticationConfigString=SOURCE=CtSecurity.CtAPCOMAuthenticationProvider.1

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter DbCompression="False"

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter DbTempoTable="True"

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter DbLoadDirectPath="False"

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter DbAdvancedDataAccess="True"

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ClientCleaningFrequency=86400 s

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ClientHeapMaxSize=1536 Mo

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ClientLeaseRenewalTime=150 s

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ClientLeaseTime=540 s

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ClientMessageReceiveTime=60 s

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter MaxServerSessionsOpenedSinceStart=5000

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter MaxServerVirtualMemory=3584 Mo

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ServerLeaseTime=500 s

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ServerLeaseRenewalTime=120 s

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ServerMessageReceiveTime=60 s

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ServerHeapMaxSize=2048 Mo

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter ServerCleaningFrequency=86400 s

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter MaxSchedulerServerTasks =

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter MaxServerTasks =

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter SchedulerComputerName =

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.start - Startup parameter IgnoreDivisionByZero = 0

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO system.transaction - Initializing the transaction manager

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO system.process - Initializing Process manager

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\Always_Before_All.sql

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO application.migration - Migration plugin : "CtMigration.dll" loaded.

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - scheme 'MAG' initialized

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - scheme 'MessFx' initialized

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - scheme 'ProcEng' initialized

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - scheme 'CtCore' initialized

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - scheme 'History' initialized

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - scheme 'APCom' initialized

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - schemes initialization end

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - schemes update beginning

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - updating scheme MAG from version 10.0.622.0 to version 10.0.623.1867

03-02-15 11:27:46 PID=5448 THD=468 USR= MSG=0 INFO ctdb.schema - updating scheme MAG

03-02-15 11:27:47 PID=5448 THD=468 USR= MSG=10027 ERROR system.database - ORA-00942: table or view does not exist§ORA-06512: at line 13

03-02-15 11:27:47 PID=5448 THD=468 USR= MSG=10077 ERROR ctdb.schema - Failed to update schema MAG.

---------------------------------------------------

The process doesn't find the script Always_Before_All.sql because it's in another path:

D:\SAP BusinessObjects\Financial Consolidation\Sql\Oracle\ instead of

D:\SAP BusinessObjects\Financial Consolidation\Sql\

I tried to copy this file into the path "Sql\" but it didn't work:

---------------------------------------------------

03-02-15 11:37:01 PID=7300 THD=7112 USR= MSG=0 INFO application.migration - Migrating application server

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Initializing application server, datasource="BOFCDEV", version=10.0.0

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter DbConnectionString="Provider="OraOLEDB.Oracle";Data Source="TB5";User ID="BOFCDEV";Password="****""

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ProductName=Finance

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ExternalAuthenticationConfigString=SOURCE=CtSecurity.CtBOBJAuthenticationProvider.1;CMS_NAME=v056v0;

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter InternalAuthenticationConfigString=SOURCE=CtSecurity.CtAPCOMAuthenticationProvider.1

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter DbCompression="False"

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter DbTempoTable="True"

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter DbLoadDirectPath="False"

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter DbAdvancedDataAccess="True"

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ClientCleaningFrequency=86400 s

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ClientHeapMaxSize=1536 Mo

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ClientLeaseRenewalTime=150 s

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ClientLeaseTime=540 s

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ClientMessageReceiveTime=60 s

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter MaxServerSessionsOpenedSinceStart=5000

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter MaxServerVirtualMemory=3584 Mo

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ServerLeaseTime=500 s

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ServerLeaseRenewalTime=120 s

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ServerMessageReceiveTime=60 s

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ServerHeapMaxSize=2048 Mo

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter ServerCleaningFrequency=86400 s

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter MaxSchedulerServerTasks =

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter MaxServerTasks =

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter SchedulerComputerName =

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.start - Startup parameter IgnoreDivisionByZero = 0

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO system.transaction - Initializing the transaction manager

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO system.process - Initializing Process manager

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\Always_Before_All.sql

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO application.migration - Migration plugin : "CtMigration.dll" loaded.

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - scheme 'MAG' initialized

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - scheme 'MessFx' initialized

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - scheme 'ProcEng' initialized

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - scheme 'CtCore' initialized

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - scheme 'History' initialized

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - scheme 'APCom' initialized

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - schemes initialization end

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - schemes update beginning

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - updating scheme MAG from version 10.0.622.0 to version 10.0.623.1867

03-02-15 11:37:02 PID=7300 THD=7112 USR= MSG=0 INFO ctdb.schema - updating scheme MAG

03-02-15 11:37:03 PID=7300 THD=7112 USR= MSG=10027 ERROR system.database - ORA-00942: table or view does not exist§ORA-06512: at line 13

03-02-15 11:37:03 PID=7300 THD=7112 USR= MSG=10077 ERROR ctdb.schema - Failed to update schema MAG.

---------------------------------------------------

Best Regards,

Ernaldo Cezar

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Accepted Solutions (1)

Hi colleagues,

We found a solution.

We had to implement SP16 Patch 1 and execute the following SQL script for each datasource in order to add the missing columns from SP15:

ALTER TABLE "CT_USER" ADD

(

"LAST_CONNECTION_DATE" DATE,
"DEFINED_RESTRICTION" NUMBER(2,0)

);

After the execution of the scripts we were finally able to migrate and start the datasources.

Best regards,

Ernaldo

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Answers (2)

Answers (2)

This will be fixed in SP16 patch 1

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

It's still not working.

We implemented the SP15, SP16 and SP16 Patch 1.

Now I'm getting another error message by the migration:

Die Ausführung der Abfrage der Datenbank ist fehlgeschlagen:

'SELECT a1.id, a1.owner_site, a1.name, a1.login_name, a1.user_type,

a1.user_active, a1.user_power, a1.user_pwd_key, a1.user_alias,

a1.last_connection_date, a1.defined_restriction FROM ct_user a1 WHERE (upper

(a1.login_name) = ?)'.

ORA-00904: "A1"."DEFINED_RESTRICTION": invalid

identifier

I'm quite sure that the problem is because we didn't migrate the datasources after implementing SP15 according to Note 2096492 (BOFC10: Database structure change introduced by SP15).

Now it's funny, I can't migrate on SP15 because I need SP16 Pach 1.

In the other hand, I can't migrate on SP16 Patch 1 because it's necessary to migrate on SP15.

Regards,

Ernaldo

Hi Ernaldo,

What is your previous SP version before you apply SP15.

Best regards,

Yang Yang

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Yang,

We had SP14.

Yesterday we tried to patch our system with the brand new SP16.

It's still not working, .

Regards,

Ernaldo

Hi Ernaldo,

That is very strange.

BFC changed the table structure in SP15 so the migration is necessary.

What about doing the migration directly after applying SP15 but not SP15 patch3.

I suggest you uninstall patch3 and SP15, then reinstall SP15 and do the migration.

Best regards,

Yang Yang

Hi Yang,

Thanks for your idea. But it didn't work.

1. I uninstalled SP16, SP15P3, SP15P1 and SP15.

2. I was able to start and migrate the datasources again with SP14.

3. I installed SP15

4. I get again the error message: "Failed to update schema MAG."

Regards,

Ernaldo

It seems that the migration's process doesn't find the sql scripts:

03-05-15 13:02:02 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\Always_Before_All.sql

03-05-15 13:02:04 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\APCom_Before.sql

03-05-15 13:02:05 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\ct_user_serial.sql

03-05-15 13:04:19 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\APCom_After.sql

03-05-15 13:04:19 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\CtCore_Before.sql

03-05-15 13:04:24 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\ct_period_month.sql

03-05-15 13:04:25 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\CtCore_After.sql

03-05-15 13:04:25 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\History_Before.sql

03-05-15 13:04:25 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\History_After.sql

03-05-15 13:04:26 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\ProcEng_Before.sql

03-05-15 13:04:27 PID=2248 THD=5172 USR= MSG=0 INFO ctdb.schema - no migration script found with name D:\SAP BusinessObjects\Financial Consolidation\Sql\ProcEng_After.sql

Regards,

Ernado

Hi Ernaldo,

Could you please confirm if these .sql file is in the SQL folder?

Best regards,

Yang Yang

Hi Yang,

All the .sql files relevant for our system are located in the folder "D:\SAP BusinessObjects\Financial Consolidation\Sql\ORACLE\". But somehow the migration process tries to reach them at the folder "D:\SAP BusinessObjects\Financial Consolidation\Sql\".

But I don't think it could be the problem.

We did a very interesting test again:

1. I uninstalled SP15

2. I was able to start and migrate the old datasource (BOFCDEV) with SP14

3. I created a new datasource called BOFCTST

4. I installed SP15

The datasource BOFCTST could be migrated.

The datasource BOFCDEV didn't work.

There is something very special with SP15.

I created an OSS message.

SAP must help us on this issue.

Regards,

Ernaldo

Ask a Question