Long running time at system copy

Hi All,
I met a problem while performing system copy. system environment is: win server 2003 Oracle 10g
the export process runs smoothly until the 19th package be exported.
18 out of 19 package have been exported successfully.
The last package is SAPSSEXEC.XXX, I checked the log file and found it runs for long time on table IGORA, PERMISSION, REPOSRC. IGORA took 2 hours more, PERMISSION took 4 hours, and REPOSRC still havn't been completed due to it contains 20 million records, but strange is that IGORA only contains 15 entries, why it took so long? and as checked in SE11, this table doesn't contain any LONG type field.
before system export, I already updated oracle statistics.
I have read through sap note:
Note 1046103 - ORACLE DIRECT PATH LOAD SUPPORT IN R3LOAD 7.00 AND LATER
Note 936441 - Oracle settings for R3load based system copy
Note 1045847 - ORACLE DIRECT PATH LOAD SUPPORT IN R3LOAD7
But seems not helpful.
Could any expert help me?
Thank you very much

Hi,
You can compare REPOSRC.log and REPOSRC.log.bck file it's copying or not.
Check the SIZE of the tables.
The Below points will use to increse the system performance while exporting.
1. Using of RowID splitting for large transparent tables (PL/SQL Script) (Table spliiting)
3. Increasing CPU/RAM in the Source hardware.
4. Editing DDLORA.TPL file for reducing index creation of import, copy parameter from DDLORA_LRG.TPL file
5. delete data from batch logs table (APQD, EDI40, TST03....)
6. Update Full statistics before export using the below br command
Brcoonect -c -u / -f stats -t all -f collect -p <number of CPU>
7. Disable archiving in database
(alter database noarchivelog)
8. PSAPTEMP adjustments , DB parameters as per the note 936441
9. for oracle slow I /O performance check the note 834343, 793113
Regards,
Ram

Similar Messages

F4 on Variable Screen for a DataStore Object Produces Long Run Time

We experiencing a long run time in returning values when we select F4 for the Variable 0COMP_CODE when we process query for a DataStore. Before our upgrade to NW04S, we did not experience this issue. As background, the DataStore (ODS) has not changed, the variable has not changed, and the query has not changed.
0COMP_CODE has the following configuration in RSD1:
Query Def. Filter Value Selection Values in Master Data Table
Query Execution Filter Val. Selectn Only Posted Values for Navigation.
These settings are exactly like this in our BW 3.5 system.
In my review of the differences, I found that in BW 3.5, the runtime is short because the selection that is returned is the Company Codes in the Master Data table, but in NW04S, the selection that is returned is the Company Codes within the ODS.
Has anyone experienced this before and if so what was your resolution?
Thanks!

Query Execution Filter Val. Selection should help you a lot in improving performance for F4.
Three options are available for the Query Execution Filter Val. Selection field on the BEx tab that directly affect F4 searches.
The Only Posted Values for Navigation setting limits an F4 search to the values related to the querys navigation state. It is the recommended setting if youre working with less savvy BW end users who may have trouble identifying applicable values or are confused when faced with long lists of characteristics. This setting yields the slowest performance in terms of the F4 search.
Only Values in InfoProvider is a better option if you need a list of characteristic values for a variable that is limited to the transactional records in the InfoProvider that a query is being executed against. This setting is ideal for restricting users to the appropriate source when data is available in different InfoProviders with different values. For example, lets say you have an InfoCube with billing data for Europe and another for the US. Each sales office will have different values, so by using this setting a variable can be restricted to the correct values.
The Values in Master Data Table setting allows users to list all possible characteristic values when they run F4. Recommend that you use it when you have transactional records for almost all the values across InfoProviders and users are aware of the relevance of the values for the navigation state.
While the Values in Master Data Table setting is the fastest F4 search setting, you need to be aware of a couple of situations when using it. Users with authorization restrictions may have an F4 list returned with all the values from the master data table, but a subsequent query may not report the result. Instead it will generate an error message informing the user of the authorization restriction. Likewise, users may select values from the master data table that are not valid for the current query due to other restrictions. There may not be any records for an InfoObject in its underlying InfoProvider designed for a query, so the system returns a no applicable data found message.
Important Notes for F4 - Performance -
748623 Input help (F4) has a very long runtimerecommendations
661251 Filter value selection displays too few/too many values
581802 Variable dialog boxes: performance of the F4 help
581079 Performance for the F4 help of navigation attributes
626887 F4 variables and InfoObject settings.
Hope it Helps
Chetan
@CP..

Error while running sapinst for system copy

Hi all,
For system copy activity of our ECC 6 system, we ran sapinst to take data export but it is not getting started and giving error "Login in process error -
An attempt to write to socket 1684 failed; reason: This application has requested the runtime to terminate it in an unusual way."
Any idea how to fix this !!!!!!
Thanks & Regards,
Pavan I

Hi,
Here is my opinion on this error, please try this out if you have downtime on your ECC system.
1. Reboot your windows system and then try exporting your DB.
2. Alternatively bring down your SAP system and DB and then try running the export and see whether it is moving fine.
Keep us posted with your feedback which will help to provide you with any other additional troubleshooting points.
Best Regards,
Vasanth G

System Refresh: Running SE09 after system copy

Hi,
After system reresh we run SE09 and delete TMS configuration of the source system as it has came to destination after database restore.
My question is is there any specific reason that we do it in SE09 only because otherwise we can simply configure TMS using STMS.
Regards
Shubham

Hello Shubham
Its SE06 not SE09 where you do this.
When you do go to SE06 and click on post activity button it basically deletes the association of source SID and attaches the target SID.
It also ensures there are no other system in that SAP Landscape with same SID.
Kindly refer to this link which gives some more information on this.
http://help.sap.com/saphelp_40b/helpdata/pt/57/38de814eb711d182bf0000e829fbfe/content.htm
Regards
Vivek

How to start a long running program at system start and stop at login and restart at logoff

I am trying to mine some crypto currency with my computer. My computer is usually in logged off state, so I want to mine automatically when system is in this state.
Untill now I have done this:
At system start, I have scheduled a task to start the mining software
at login I have scheduled another task to kill the mining process
Here comes the question: I need to restart the mining process as soon as the user logs off.
But I couldnt figure out how to schedule a task at logoff, so I decided to use Group Policy Ediotr's Logoff scripts. But the problem is, I can't seem to log off at all, because system seems to be waiting for the "script" to finish, and since it is
a mining process, it doesn't finish, and the user is never logged off!
How do I configure windows to resume mining after the logoff?

Hi!
I haven't been working much with mining, but you are thinking correctly with using the logon/logoff-scripts.
The problem is that the process for mining requires a user to be logged on, it runs i user-context.
So if you in some way can start the process to run in system context, you are good to go. (The mining process) But if this is possible at all I do not know, I think the miners are dependent on a user being logged on.
Best regards
Andreas Molin
Andreas Molin | Site: www.guidestomicrosoft.com | Twitter: andreas_molin

Long run time with ORDER by clause

Hi,
I am having a query which is executing fine(in 2 mins) but when i am using order by clause in it, its taking around 13 mins.
Can anyone suggest what could be th reason and how to execute the same query are get the ordered record?
thanks.

Sorry for not providing complet details.
Database version id 10g.
Below is the execution plan when using with order by clause.
Execution Plan
| Id | Operation                              | Name              | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT                       |                   |     1 |   118 | 1538 |
|   1 | FILTER                                |                   |       |       |       |
|   2 |   HASH JOIN                            |                   | 16657 | 1089K|    56 |
|   3 |    TABLE ACCESS FULL                   | FILETYP           |     6 |    60 |     3 |
|   4 |    TABLE ACCESS FULL                   | FILETYPSOURCEID   | 16657 |   927K|    52 |
|   5 |   NESTED LOOPS                         |                   |     1 |    35 |     3 |
|   6 |    TABLE ACCESS BY INDEX ROWID         | FILEWAREHOUSE     |     1 |    25 |     2 |
|   7 |     INDEX RANGE SCAN                   | FILEWAREHOUSE_DX2 |     1 |       |     2 |
|   8 |    TABLE ACCESS BY INDEX ROWID         | EXTFILE           |     1 |    10 |     1 |
|   9 |     INDEX UNIQUE SCAN                  | PK_EXTFILE        |     1 |       |     1 |
| 10 | SORT ORDER BY                         |                   |     1 |   118 | 1538 |
| 11 |   NESTED LOOPS                         |                   |     1 |   118 | 1534 |
| 12 |    NESTED LOOPS OUTER                  |                   |     1 |   100 | 1533 |
| 13 |     NESTED LOOPS OUTER                 |                   |     1 |    96 | 1532 |
| 14 |      NESTED LOOPS                      |                   |     1 |    88 | 1531 |
| 15 |       HASH JOIN                        |                   |     5 |   360 | 1524 |
| 16 |        TABLE ACCESS BY INDEX ROWID     | RTXN              |     1 |    22 |     1 |
| 17 |         NESTED LOOPS                   |                   |   117 | 5148 | 1518 |
| 18 |          VIEW                          | VW_SQ_1           | 20869 |   448K| 1441 |
| 19 |           HASH GROUP BY                |                   | 20869 |   427K| 1441 |
| 20 |            FILTER                      |                   |       |       |       |
| 21 |             TABLE ACCESS BY INDEX ROWID| RTXNSTATHIST      | 20869 |   427K| 1304 |
| 22 |              INDEX RANGE SCAN          | RTXNSTATHIST_DX2 | 20869 |       |    29 |
| 23 |          INDEX RANGE SCAN              | PK_RTXN           |     1 |       |     1 |
| 24 |           NESTED LOOPS                 |                   |     1 |    24 |     3 |
| 25 |            TABLE ACCESS BY INDEX ROWID | FILEWAREHOUSE     |     1 |    14 |     2 |
| 26 |             INDEX RANGE SCAN           | FILEWAREHOUSE_DX2 |     1 |       |     2 |
| 27 |            TABLE ACCESS BY INDEX ROWID | EXTFILE           |     1 |    10 |     1 |
| 28 |             INDEX UNIQUE SCAN          | PK_EXTFILE        |     1 |       |     1 |
| 29 |        TABLE ACCESS FULL               | RTXNTYP           |     1 |    28 |     5 |
| 30 |       TABLE ACCESS BY INDEX ROWID      | RTXNSTATHIST      |     1 |    16 |     2 |
| 31 |        INDEX RANGE SCAN                | PK_RTXNSTATHIST   |     1 |       |     1 |
| 32 |      TABLE ACCESS BY INDEX ROWID       | NTWKNODE          |     1 |     8 |     1 |
| 33 |       INDEX UNIQUE SCAN                | PK_NTWKNODE       |     1 |       |     1 |
| 34 |     INDEX UNIQUE SCAN                  | PK_ORG            |     1 |     4 |     1 |
| 35 |    TABLE ACCESS BY INDEX ROWID         | ACCT              |     1 |    18 |     1 |
| 36 |     INDEX UNIQUE SCAN                  | PK_ACCT           |     1 |       |     1 |
Below is the execution plan when running without ORDER BY clause...
Execution Plan
| Id | Operation                             | Name              | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT                      |                   |     1 |   135 | 1537 |
|   1 | FILTER                               |                   |       |       |       |
|   2 |   HASH JOIN                           |                   | 16657 | 1089K|    56 |
|   3 |    TABLE ACCESS FULL                  | FILETYP           |     6 |    60 |     3 |
|   4 |    TABLE ACCESS FULL                  | FILETYPSOURCEID   | 16657 |   927K|    52 |
|   5 |   NESTED LOOPS                        |                   |     1 |    35 |     3 |
|   6 |    TABLE ACCESS BY INDEX ROWID        | FILEWAREHOUSE     |     1 |    25 |     2 |
|   7 |     INDEX RANGE SCAN                  | FILEWAREHOUSE_DX2 |     1 |       |     2 |
|   8 |    TABLE ACCESS BY INDEX ROWID        | EXTFILE           |     1 |    10 |     1 |
|   9 |     INDEX UNIQUE SCAN                 | PK_EXTFILE        |     1 |       |     1 |
| 10 | NESTED LOOPS                         |                   |     1 |   135 | 1534 |
| 11 |   NESTED LOOPS OUTER                  |                   |     1 |   117 | 1533 |
| 12 |    NESTED LOOPS OUTER                 |                   |     1 |   113 | 1532 |
| 13 |     NESTED LOOPS                      |                   |     1 |   105 | 1531 |
| 14 |      HASH JOIN                        |                   |     5 |   445 | 1524 |
| 15 |       TABLE ACCESS FULL               | RTXNTYP           |     1 |    28 |     5 |
| 16 |       TABLE ACCESS BY INDEX ROWID     | RTXN              |     1 |    22 |     1 |
| 17 |        NESTED LOOPS                   |                   |   117 | 7137 | 1518 |
| 18 |         VIEW                          | VW_SQ_1           | 20869 |   794K| 1441 |
| 19 |          HASH GROUP BY                |                   | 20869 |   427K| 1441 |
| 20 |           FILTER                      |                   |       |       |       |
| 21 |            TABLE ACCESS BY INDEX ROWID| RTXNSTATHIST      | 20869 |   427K| 1304 |
| 22 |             INDEX RANGE SCAN          | RTXNSTATHIST_DX2 | 20869 |       |    29 |
| 23 |         INDEX RANGE SCAN              | PK_RTXN           |     1 |       |     1 |
| 24 |          NESTED LOOPS                 |                   |     1 |    24 |     3 |
| 25 |           TABLE ACCESS BY INDEX ROWID | FILEWAREHOUSE     |     1 |    14 |     2 |
| 26 |            INDEX RANGE SCAN           | FILEWAREHOUSE_DX2 |     1 |       |     2 |
| 27 |           TABLE ACCESS BY INDEX ROWID | EXTFILE           |     1 |    10 |     1 |
| 28 |            INDEX UNIQUE SCAN          | PK_EXTFILE        |     1 |       |     1 |
| 29 |      TABLE ACCESS BY INDEX ROWID      | RTXNSTATHIST      |     1 |    16 |     2 |
| 30 |       INDEX RANGE SCAN                | PK_RTXNSTATHIST   |     1 |       |     1 |
| 31 |     TABLE ACCESS BY INDEX ROWID       | NTWKNODE          |     1 |     8 |     1 |
| 32 |      INDEX UNIQUE SCAN                | PK_NTWKNODE       |     1 |       |     1 |
| 33 |    INDEX UNIQUE SCAN                  | PK_ORG            |     1 |     4 |     1 |
| 34 |   TABLE ACCESS BY INDEX ROWID         | ACCT              |     1 |    18 |     1 |
| 35 |    INDEX UNIQUE SCAN                  | PK_ACCT           |     1 |       |     1 |
-------------------------------------------------------------------------------------------Edited by: user10754555 on Feb 5, 2010 6:02 PM

Infoset Query - Long run times

Hi All,
I was running a Bex query on top of an infoset query a few days ago with no problems and very good performance. Now, returning any number of records it runs and timesout. I know that there will be recommendations related to statistics and possibly those related to the active table of the ODS. I have checked these and they have been recently updated. In fact, when I manually update the statistics the behaviour is the same. The structure of the infoset has not changed.
We are running 3.0B on DB2.
Any ideas?
Robert Zovic
Arinso International

Hi Giridharan,
you check whether the hierarchy SIDs are updated properly, structure, to date are all fine.
check the difference between X and Y hierarchy.
Regards,
Prakasha A

Homogeneous System Copy failing on Phase Running J2EE Migration

Hi All,
I am running a Homogeneous System Copy according to the System Copy manual. (SAPinst not SV/RST) It is failing on Phase Running J2EE Migration which tells me to look at my RUNJMT.log (below), but it doesn't seem to give me much direction. As anyone run into this before?:
An error occurred while processing service SAP NetWeaver 7.0 Support Release 3 > Software Life-Cycle Options > System Copy > IBM DB2 for i5/OS > Target System Installation > Central System > Based on AS ABAP and AS Java > Central System( Last error reported by the step :Error when running the Java Migration Toolkit. SOLUTION: See output of logfile Y:\usr\sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS//runJmt.log: ' com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server, at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108) at com.sap.engine.core.configuration.impl.cache.CachedConfiguration. (CachedConfiguration.java:62) at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848) at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882) at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748) at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734) at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693) at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54) at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108) at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174) at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129) at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403) at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)'.). You may now
choose Retry to repeat the current step.
choose View Log to get more information about the error.
stop the task and continue with it later.
Log files are written to Y:\usr\sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/.
runjmt.log:
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server,
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)
 at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
 at java.lang.reflect.Method.invoke(Method.java:391)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Here is version '9' fo the SAPinst.log
INFO 2010-06-15 09:20:24.952
Creating file Y:\usr\sap\SAPinst\NW04S\LM\COPY\DB4\SYSTEM\CENTRAL\AS\x.
INFO 2010-06-15 09:20:24.952
Removing file Y:\usr\sap\SAPinst\NW04S\LM\COPY\DB4\SYSTEM\CENTRAL\AS\x.
INFO 2010-06-15 09:21:12.656
Creating file C:\Program Files (x86)\SAPinst\x.
INFO 2010-06-15 09:21:12.656
Removing file C:\Program Files (x86)\SAPinst\x.
INFO 2010-06-15 09:21:28.313
Copied file 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.xml' to 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.24.xml'.
INFO 2010-06-15 09:21:39.798
Copied file 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.xml' to 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.25.xml'.
WARNING 2010-06-15 09:22:11.095
Unable to get information about path
LABEL.ASC\ using GetVolumeInformation. Operating system error message: The filename, directory name, or volume label syntax is incorrect.
INFO 2010-06-15 09:22:18.595
Copied file 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/inifile.xml' to 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/inifile.9.xml'.
INFO 2010-06-15 09:22:23.798
Copied file 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/keydb.xml' to 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/keydb.9.xml'.
INFO 2010-06-15 09:22:38.814
Copied file 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.xml' to 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.26.xml'.
INFO 2010-06-15 09:22:45.908
Execute step RunMigrationController of component |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0
INFO 2010-06-15 09:23:25.675
Creating file Y:\usr\sap\SAPinst\NW04S\LM\COPY\DB4\SYSTEM\CENTRAL\AS\runJmt.log.
INFO 2010-06-15 09:23:32.175
Working directory changed to Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/jmt.
INFO 2010-06-15 09:23:39.800
Working directory changed to Y:\usr\sap\SAPinst\NW04S\LM\COPY\DB4\SYSTEM\CENTRAL\AS.
INFO 2010-06-15 09:23:39.956
Removed environment variable JANITOR_400 from current process environment.
INFO 2010-06-15 09:23:44.878
Output of \qopensys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath /usr/sap/BID/SYS/global/sltools/sharedlib/launcher.jar;. com.sap.engine.offline.OfflineToolStart com.sap.sdt.jmt.migrationtool.MigrationToolImport /usr/sap/BID/SYS/global/sltools/jmt:/usr/sap/BID/SYS/global/sltools/sharedlib import.switch resume downtime mti.properties is written to the logfile Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/runJmt.log.
WARNING 2010-06-15 09:23:45.456
Execution of the command "\qopensys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath /usr/sap/BID/SYS/global/sltools/sharedlib/launcher.jar;. com.sap.engine.offline.OfflineToolStart com.sap.sdt.jmt.migrationtool.MigrationToolImport /usr/sap/BID/SYS/global/sltools/jmt:/usr/sap/BID/SYS/global/sltools/sharedlib import.switch resume downtime mti.properties" finished with return code 2. Output:
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server,
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)
 at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
 at java.lang.reflect.Method.invoke(Method.java:391)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
ERROR 2010-06-15 09:23:45.534
CJS-20068 Error when running the Java Migration Toolkit. SOLUTION: See output of logfile Y:\usr\sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS//runJmt.log: '
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server,
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)
 at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
 at java.lang.reflect.Method.invoke(Method.java:391)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)'.
ERROR 2010-06-15 09:23:45.534
CJS-20068 Error when running the Java Migration Toolkit. SOLUTION: See output of logfile Y:\usr\sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS//runJmt.log: '
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server,
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)
 at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
 at java.lang.reflect.Method.invoke(Method.java:391)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)'.
ERROR 2010-06-15 09:23:46.644
FCO-00011 The step RunMigrationController with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|RunMigrationController was executed with status ERROR ( Last error reported by the step :Error when running the Java Migration Toolkit. SOLUTION: See output of logfile Y:\usr\sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS//runJmt.log: '
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server,
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)
 at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108)
 at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403)
 at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
 at java.lang.reflect.Method.invoke(Method.java:391)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)'.).
INFO 2010-06-15 09:26:38.491
An error occured and the user decide to stop.\n Current step "|NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|RunMigrationController".
INFO 2010-06-15 09:29:23.322
Creating file C:\Program Files (x86)\SAPinst\.lastInstallationLocation.
INFO 2010-06-15 09:29:29.510
Creating file Y:\usr\sap\SAPinst\NW04S\LM\COPY\DB4\SYSTEM\CENTRAL\AS\__instana_tmp.xml.

Run-time vs. System errors

Whats the a good way to tell the difference between run-time and system errors.

Inkisar.a wrote:
Whats the a good way to tell the difference between run-time and system errors.
Exceptions

ABAP Run time error while doing MIR6

Hi,
We are processing posting parked invoice & system did not displays the document & after then it throws long run time error.
regards,
mahesh

Hi,
Such run time errors occur if you are trying to process huge data or if the system is being accessed by too many users and if there are any foreground jobs run in the sap for huge data. Infact go to /tcode ST22 and check for the detailed error message and try executing the tcode after some time and also check if there are any jobs which have been scheduled in the foreground.
hope this helps
regards,
radhika

NiDAQ 6008 -- Long running task stability

I have a small C program using nidaqmxbase, based on the example code provided.
This runs with a usb connected 6008 on a Red Hat Linux machine. The task is simple, read the analog voltage (differential, reference source 2.5v range) from one channel at 1000hz in blocks of 50 samples. The results are placed into network messages to send to another program for analysis.
This program works fine, but has a long run-time stability issue when left running for more than about 24 hours continuously (and, for my application I need to capture in realtime 24/7 indefinitly). The symptom observed is that the 6008 stops returning data -- and "lsdaq" shows that the device is no longer seen by the system. Sometimes the green LED stops blinking as well. Has the DAQ crashed? Did some counter overflow and cause the driver to malfunction? I am able to restore function only by physically disconnecting and re-connecting the 6008.
Thank you
Andy.

Hi aws-
It sounds like the problem you are seeing could be related to bus powering or resource conflicts on your system. The fact that the failure results in total loss of connectivity with your device certainly seems to indicate a hardware problem.
You said your code is based on the example code; please verify if an unmodified shipping example fails similarly. If so, please let us know which program fails and I will attempt to replicate the issue here. Do you see this problem on multiple computers and/or with multiple USB-6008 devices?
Thanks-
Tom W
National Instruments

Long running ACT_UPG during EHP4 (SP-Stack 08)

During EHP4 Installation after a installation of ERP 6.0 EHP4 Ready) ACT_UPG is running , but very slowly.
In a different system (linux on intel cpu) it took only 6 hours. In my actual system it is already running since nearly 13 hours- since 08.11.2010 04:35:58 !
I compared the actually written logfile
/sapmnt/D01/EHPI/abap/tmp$ wc -l SAPAA70104.D01
588286 SAPAA70104.D01
with that one from a finished installation on linux (with lower sp-stack than 08 and older sapehpi)
There the file has 1.451.798 rows, which means that my ACT_UPG has more than the same work to do...
I have checked the shadow instance: 4 batchprocesses- only one is running with RDDMASGL since 08.11.2010 04:35:58
Add. information:
-Database and CI are on separate hosts (solaris sparc). Both are inclued in /etc/hosts.
- I used sapehpi version SAPehpi_38-10005811.SAR - SAPehpi 700 from 21.10.2010
- I have used following settings :
SAPehpiConsole.log:
Enter the maximum number of batch processes during the installation:
BATCH PROCESSES: 3
Enter the maximum number of parallel processes during uptime:
MAXIMUM UPTIME PROCESSES: 3
Enter the number of parallel import processes during downtime:
R3TRANS PROCESSES: 3
To optimize memory usage during activation, you can use the so-called
"memory-optimized activator". Do you want to use this possibility?
01) - Yes
02) * No
: No
Any ideas ?
Uta
Edited by: Uta Hedemann on Nov 9, 2010 5:34 PM

problem solved itself. ACT_UPG is finished
The corresponding logfile seems to be invalid for analyzing the runtime . Much more smaller than on the other system on linux....
/sapmnt/D01/EHPI/abap/log$ wc -l SAPAA70104.D01
617706 SAPAA70104.D01
Good luck for everybody who has also long run times!
Edited by: Uta Hedemann on Nov 9, 2010 6:26 PM

Does OS effective battery run time/life?

I really do not have a preference to which OS that I use, either XP Pro or Vista Business (although have never used Vista before) but I am wondering if using one verse the other would help increase and stretch the battery life. If all things being equal as far as functions, radios turned on, screen brightness and such, will one give me longer run times than the other?
I have read a few entries and there seems to be more updates, revisions and features are being developed and put into Lenovo's management systems for Vista, so I am wondering if perhaps that would have any difference as well.
One more thing, has there been any updates/upgrades since Feb or March that would make a difference in the run time of the battery life with either Vista, XP or any of the Lenovo management systems? I ask because I read the review at notebookreview and I was shocked that they only got about 3 1/2 to 4 hours of use from the X300 and the T400 is getting over 6 1/2 hours and both machines are using 6 cell batteries.

Hello DanMgy,
Vista out of the box and without tweaks like disabling aero or the sidebar may consume more power,
than an normal XP.
But Vista will give you more options to safe power, and a well tweaked Vista, seems more effective
than a normal XP. But in this case, it will problably having the look, as good old XP.
Follow @LenovoForums on Twitter! Try the forum search, before first posting: Forum Search Option
Please insert your type, model (not S/N) number and used OS in your posts.
I´m a volunteer here using New X1 Carbon, ThinkPad Yoga, Yoga 11s, Yoga 13, T430s,T510, X220t, IdeaCentre B540.
TIP: If your computer runs satisfactorily now, it may not be necessary to update the system.
English Community Deutsche Community Comunidad en Español

Does OS effect battery run time/life?

I really do not have a preference to which OS that I use, either XP Pro or Vista Business (although have never used Vista before) but I am wondering if using one verse the other would help increase and stretch the battery life. If all things being equal as far as functions, radios turned on, screen brightness and such, will one give me longer run times than the other?
I have read a few entries and there seems to be more updates, revisions and features are being developed and put into Lenovo's management systems for Vista, so I am wondering if perhaps that would have any difference as well.
One more thing, has there been any updates/upgrades since Feb or March that would make a difference in the run time of the battery life with either Vista, XP or any of the Lenovo management systems? I ask because I read the review at notebookreview and I was shocked that they only got about 3 1/2 to 4 hours of use from the X300 and the T400 is getting over 6 1/2 hours and both machines are using 6 cell batteries.

As a rule of the thumb, XP gives better battery life than Vista, at least on the machines that I've had both on which would include T42p, T43p, X61s (ultralight LCD) and T61p.
Hope this helps.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

Recovery failed during homognuos System copy maxdb 7.7 red hat 5.4 ECC 6.0

Hi all,
         *Actully i have one Development Server with ECC 6.0.. + maxdb 7.7 database    OS Red Hat 5.4.
Please help us to what username and password we can give....i am from oracle backgroud so i am a newbie in maxdb.
Source System
ECC 6.0
OS Redhat 5.4
SAPSID   WIA
Target system
ECC 6.0
OS Redhat   5.4
SAPSID    WID
Now i am going to Create Quality Server for my landscape using homogenoues system copy ....option in target machine... and I have taken database backup (offline backup) also...
But during system copy it is asking for Database recovery . For recovery i am using DATABASE MANAGER TOOL (DBMGUI 7.6 maxdb) but it is asking for IP ,DBname username and password.
I have given the IP and DB Name but dont know the username and password for the target Machine SAPSID
Because at the time of system copy it asked for database recovery before creating the database users phase .
I checked with xuser list from command line it is showing no values.
Tried with the username and password given at OS level and the password for Source system but no luck.
So what to do.....
Please help

Hi,
thanks for your reply.
I am sahil garg and amkum82 user we both are working on the same issue.
We both are from oracle backgroud.Newbie in maxdb.
We have are following the 129352 note for homogenous system copy.
      2. Target system:
            b) Restore:
            Before the restore, you must initialize the target instance. This initialization formats the log area. Data volumes are only formatted if they are not configured as raw devices and are not available in the configured size.
            We dont know how to create instancefor tarhet system in maxdb for homogenues system copy.Could you please help us out what steps needed to be executed for this.
Thanks Regards,
Sahil

Long running time at system copy

Similar Messages

Maybe you are looking for