-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- SAP Business Suite
- Artificial Intelligence
- Business applications
- Data and analytics
- Technology Platform
- Financial Management
- Spend Management
- Supply Chain Management
- Human Capital Management
- Customer Experience
- SAP Business Network
- View products A-Z
- View industries
- Try SAP
- Partners
- Services
- Learning and Support
- About
- SAP Community
- Groups
- Interest Groups
- Application Development and Automation
- Discussions
- Error on Table copying from Prod to Dev Server
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Error on Table copying from Prod to Dev Server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2009 Jul 20 7:31 AM
- SAP Managed Tags
- ABAP Connectivity
Hello Experts!
I'm copying a table from Prod to Dev Server, but i'm having a system error!
IMP-00058: ORACLE error 60 encountered
ORA-00060: deadlock detected while waiting for resource
IMP-00028: partial import of previous table rolled back: 34196 rows rolled back
I check developers but one is using this table...
kindly show me how to unblocked this table.....or how to check why the table is locked.
Thank you very much!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2009 Jul 29 1:09 PM
- SAP Managed Tags
- ABAP Connectivity
Hi,
You can check with all these things.
Copying the Productive Client to the Development System (with Client Export/Import)
1. Make sure the source client is locked or no one is using it.
2. Log into the source client.
3. Export the source client using transaction SCC8.
4. Choose the target system D01.
5. Choose profile ZSAP_ALL.
6. Check/change the profile parameters as necessary, using the menu command Profileïƒ Change/Display
7. Schedule the export to run in the background
8. After export, check the job log (SM37) to make sure the export was successful.
9. Check to make sure the exported files exist in
dev\sapmnt\trans\data and
dev\sapmnt\trans\cofiles. The files should have a name of the form
Sxnnnnn.sid, Ronnnnn.sid, and/or Rtnnnnn.sid where nnnnn is the transport request number, and sid is the SID of the source client. The file Ronnnnn.sid contains client-independent data.
10. Adjust the rollspace (see above) of the target database.
11. Import the request SIDKOnnnnn if it exists, using the u248 options. For instance, if the request is P01KO00011, and you are importing to system D01 client 100, you would execute the commands:
tp addtobuffer P01KO00011 D01
tp import P01KO00011 D01 client=100 u248
12. Check the transport logs to make sure the import was successful.
13. Import the request SIDKTnnnnn, using the u248 options. For instance, if the request is P01KT00011, and you are importing to system D01 client 100, you would execute the commands:
tp addtobuffer P01KT00011 D01
tp import P01KT00011 D01 client=100 u248
14. Check to make sure the import was successful
15. After tp import is finished, use transaction SCC7 to start post-import processing. Check the job with SM37 to make sure it finishes successfully.
16. After SCC7 has finished (about 4 hrs), shut down and restart SAP and Oracle
17. Return the rollspace to its normal configuration
Regards,
Shamma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2009 Jul 29 1:09 PM
- SAP Managed Tags
- ABAP Connectivity
Hi,
You can check with all these things.
Copying the Productive Client to the Development System (with Client Export/Import)
1. Make sure the source client is locked or no one is using it.
2. Log into the source client.
3. Export the source client using transaction SCC8.
4. Choose the target system D01.
5. Choose profile ZSAP_ALL.
6. Check/change the profile parameters as necessary, using the menu command Profileïƒ Change/Display
7. Schedule the export to run in the background
8. After export, check the job log (SM37) to make sure the export was successful.
9. Check to make sure the exported files exist in
dev\sapmnt\trans\data and
dev\sapmnt\trans\cofiles. The files should have a name of the form
Sxnnnnn.sid, Ronnnnn.sid, and/or Rtnnnnn.sid where nnnnn is the transport request number, and sid is the SID of the source client. The file Ronnnnn.sid contains client-independent data.
10. Adjust the rollspace (see above) of the target database.
11. Import the request SIDKOnnnnn if it exists, using the u248 options. For instance, if the request is P01KO00011, and you are importing to system D01 client 100, you would execute the commands:
tp addtobuffer P01KO00011 D01
tp import P01KO00011 D01 client=100 u248
12. Check the transport logs to make sure the import was successful.
13. Import the request SIDKTnnnnn, using the u248 options. For instance, if the request is P01KT00011, and you are importing to system D01 client 100, you would execute the commands:
tp addtobuffer P01KT00011 D01
tp import P01KT00011 D01 client=100 u248
14. Check to make sure the import was successful
15. After tp import is finished, use transaction SCC7 to start post-import processing. Check the job with SM37 to make sure it finishes successfully.
16. After SCC7 has finished (about 4 hrs), shut down and restart SAP and Oracle
17. Return the rollspace to its normal configuration
Regards,
Shamma
Bluesky