STMS restriction in PRD

Dear All,
We are having the issue , If our User is having authorization in quality server for stms , they are able to do the transport in PRD also , please let us know how to restrict ..?
Regards
RK

Hi,
These are the object that you should check and adjust in roles assigned to user.
S_TRANSPRT
To secure functions that change requests and tasks.
S_CTS_ADMI
To secure the administration functions of the CTS.
Take any user from production, goto suim and search for roles assigned to user having these objects.
Edit those roles, remove authorization and generate auth profiles
Divyanshu

Similar Messages

STMS: Transport control program tp ended with error code 0232

Dear ERP Gurus,
I just encountered problem with STMS in my PRD system. The import is just stuck up on "tp connecting to database". It won't continue unitl the system gives me this error message:
Transport control program tp ended with error code 0232
Errors: connect failed
The tp System log says:
ERROR: Connect to PRD failed (20090227135454, probably wrong environment)
I have verified that the suggestion in SAP Note 165708 has already been implemented in our DEV, QAS, and PRD instances.
Any idea why I am having this problem? Imports were running fine yesterday. Please help.
Your prompt response is highly appreciated.
Thanks a lot.
Best Regards,
Albert

Hi Albert,
First check import monitor and delete all requests from queue, which are still getting imported.
And go to /usr/sap/trans/tmp and mv all those tmp files to other location.
Then kill all OS jobs which are getting execute with tp.
Check all jobs are runnig fine, related to transportation. If not reschedule the same.
Then start importing.
Before doing this just check whether your stms related RFCs are working fine.
I think One of your RFC is getting struck. just try to change ip or hostname accordingly and try.
Regards
Nick Loy

What happen when I delete STMS?

Dear gurus,
When I delete STMS configuration from all system (DEV, QA, PRD), is the stms queue also deleted?
When I reconfigure (change transport domain from DEV to QA), will the queue will be there again?
And what happen in SE01? Will the transport request will still be there in the Development system?
Thanks for your help.
Best Regards,

What if there's this scenario:
From network perspective:
Network / Port from DEV -> QA = allowed
Network / Port from QA -> PRD = allowed
Network / Port from DEV -> PRD = closed
Transport Domain is DEV.
Transport Domain Controller is QA.
When I configure STMS in Production, PRD can't be included in the transport domain.
What's the solution when we want to leave the network configuration remain unchanged?
Best Regards,

STMS Configuration - Change Virtual System with Real System

Dear all,
My system, if I go in the transaction STMS in DEV system, was configureted in the following way:
DEV => QA => PROD (Virtual System)
Now, I want to change the PROD Virtual System in PROD Real System.
How Can procede?
Can you explain step-by-step the process?
Because the system was configureted from other people, and I'm new to using the STMS.
Thanks in advanced for your help.
Best Regards,
Giulio

Hi,
After the planned system is physically installed it is time to replace the Virtual System with the realized system.
The procedure for the same is as under:
1) Delete the Virtual System from the transport domain
. Login into Transport Domain system client 000
· Using STMS got to Overview=> Systems
· Chose SAP Virtual System=> Delete (confirm)
· Distribute configuration change.
As soon as the configuration change is distributed, the virtual system is deleted. The import queue for this system in TMS disappears but it is available as import buffer at the operating systems level.
Now add the new (physical system) to the transport domain:
If STMS is configured as standalone system then first delete STMS configuration on PRD system
login into PRD system client 000. (delete STMS configuration if present.)
run stms -> it's ask for set up STMS -> click on other configurition (F6)
Target Host -> host name of domain controller ( host name of transport domain system)
System number -> Instance number of domain controller ( instance number of transport domain system)
Now,
Go to the Transport Domain Controller and accept the system. (As the import buffer is available at the operating system level, no change requests will be lost)
Distribute the configuration changes.
regards,
kaushal

The correct way to delete old transport request record ?

Dear all,
We want to delete old transport request record before 2008 (two years before) of our system.
We learn that we should delete the records in the below two path:
/usr/sap/trans/data
/usr/sap/trans/cofiles
Our target is that we will not see the old record after deleting in our PRD system.
Normally, we see the transport request record in system by this way:
STMS --> import overview --> PRD --> Import Queue system PRD --> Import history
Our question is do we need to restart our system after delete the record to refresh the Import history?
We have not delete the record now.
Any experienced or expert, please kindly give advice.
Regards,
Allen

Hello Allen,
there are some notes and documentations for this process. Deleting the files from /cofiles and /data will not erase the request from the import history, as you already know.
You should follow note #41732 to have the requests/data completely deleted from your system. There is a lot of complementary reading in notes #7224, #556734, #189841, etc.
Note that you can remove the request from the import queue, import history, data and cofiles subdirectory, but still have it on the <SID> buffer (located in /usr/sap/trans/buffer/<SID>). If this happens to you, please save a copy of the buffer file <SID>, then create a new, blank file named <SID> at a time when the import queue is empty (VERY IMPORTANT). Or, alternatively, please excute the tp cleanbuffer FIL command (which will erase the requests that are not found in /data and /cofiles directories).
--> Please test this first on a test system, not directly on a productive environment.
This should be enough to delete old transport requests on your system.
Best regards,
Tomas Black

Transport strategy for your transport landscape is inconsistent

Hello everybody,
we had 4 system landscape.
DEV>QAS>TST-->PRD.
we move the request from DDEV >QAS>TST and then forward request from TST to PRD system.
Now, we have delete the system TST from TMS, after deletion it give the warning.
Transport strategy for your transport landscape is inconsistent.
Message No. XT481
Please suggest, what is meaning of this warning and how to correct.
Thanks
Ganesh

You need to do following
1. Logon to domain controller client 000 -->STMS --> Overview System --> Select TST --> SAP System --> Delete
2. Reconfigure STMS DEV>QAS>PRD
3.STMS --> Overview Transport Routes --> Configuration --> Distribute and Activate (To All System)
Note : You should do this from Domain Controller client 000
I assumed you know Step 2. If you dont please let me know i can guide you on that as well
Cheers !
Manish

How to import transport of copies to productive systems

Hello,
I have been experiencing a problem that even the guys from admin could not solve (yet). I should say I work in a development team.
Imagine you have two landscapes, one DEV-QAS(1) to develop big projects and a normal DEV-QAS-PRD(2) landscape where my objects will be imported. After a new group of objects is finished in (1), we ask to import the workbench request in the STMS queue of DEV(2). After this, and after some small test, we create a transport of copies in DEV(2) where we include the first transport, release it and import it to the QAS(2) queue. After the tests in QAS(2) the idea would be to import the transport of copies to productive system PRD(2). But it does not work...
In STMS queue for PRD(2), there is no entry for the transport of copies. Also, when I tried to add the transport request to the import queue (via menu -> Extras -> Other requests -> Add), I get an error message stating that no co-files where found for the transport.
Does anyone know this problem? I suspect it can have sothing to do with the use of a transport of copies, but, if I don't use this kind of transport, how can I get objects from other systems to production?
Thanks in advance.
Davide Sepanas, Portugal

Davide,
Re your latest questions:
> 1) Why this problem with transport of copies doesn't happen from DEV(2) to QAS(2), since these systems are also not in the same transport directory?
>
I think the answer is in your original problem description:
we create a transport of copies in DEV(2) where we include the first transport
>
When you create a transport of copies you must indicate a terget system and I suppose you enter QAS(2) there. In that case the TMS will add the request to the import buffer of the target system when you export the request from DEV(2). I understand that you never have to add transports of copies to the import buffer of QAS(2) manually, which proves the TMS does this for you. However, for further imports into systems that are not designated as target system of the transport of copies, like PRD(2), the TMS will do nothing of the sort and you must add the request to the queue yourself - which in your case also means you have to forward the transport files first.
> Can we assume, then, that, where I was working before, all three systems were configured in the same transport directory, avoiding thus the problem with the transport of copies requests?
Yes, and that is the most common way of setting up the transport system. Having separate transport systems really only makes sense when sharing the transport directory between the dev, qas and prd systems (via NFS for UNIX, via network shares for Windows) is not possible, either because there is no local network between the servers or because some security policy forbids it. I'd advise you to certainly ask the question to your system admin.
Regards,
Mark

Dev and Qty import queue is empty

Hi All,
We are having three system landscape Dev, Qty and Prd. In STMS we configured PRD as a virtual system. We have released some requests in Dev 15 days back & we are not imported and we are able see the requests in STMS_IMPORT of Qty. But suddenly when we are checking now there are no requests in QTY stms_import and DEV stms_import as well.
We have checked all the checks STMS and we manually checked wether trans directory of Domain controller also accessing from QTY.
Please suggest on the issue.
Thanks & Regards,
Sreekanth

Hi All,
I have reconfigured STMS. Still when i am adding released request with tp command to the buffer of QTY its not showing in import queue. While when i added to the DEV buffer the request is showing in queue but not to QTY.
When i checked consistency check for DEV it showing 4KB of datafile and 1KB of cofile, but when checked for QTY it showing 0 KB for data and cofile. But all folders in trans of domain controller are accessible from QTY, even all checks are showing the same trans directory of domain controller.
Please suggest.
Best Regards,
Sreekanth

IMPORT ERROR : RFC Error

Dear Experts,
I have successfully upgraded Kernal Version from 129 to 175 in SAP ERP ECC 5.0, but when i am importing the queue the following error is coming.
System PRD
Command TMS_MGR_READ_TRANSPORT_QUEUE
Client 000 Service
Transport Service User TMSADM
Start Online
Date 03.08.2007
Function TMS_TP_SHOW_BUFFER
Time 13:49:42
Message TP_CALL_FAILED
Could not start transport control program tp
RFC error:
My SAP Version: ECC 5.0
DB : MS SQL SERVER 8.0
OS : WINDOWS NT
Please help me to find out the solution.
Regards,
Praveen Merugu

Hi ,
I m VASU, basis consultant from Bangalore.
I m unable to get the IMPORT QUEUE in STMS.
System PRD
Command TMS_MGR_READ_TRANSPORT_QUEUE
Client 000 Service
Transport Service User TMSADM
Start Online
Date 03.08.2007
Function TMS_TP_SHOW_BUFFER
Time 13:49:42
Message TP_CALL_FAILED
Could not start transport control program tp
RFC error:
My SAP Version: ECC 5.0
DB : MS SQL SERVER 2005.
OS : WINDOWS NT
I saw ur MSG in this forum....
Plzzz guide me how to reolve this issue at OS level...
I have tried updating the KERNAL level 142 to 175 , but still TP is not connecting.
Rest of all work in PRD is working fine ...only TP is not working due to this REQUESTS r not getting imported into PRD.
Tested tp connect <PRD> , R3trans -d, both were not giving any error..
Waiting for ur reply
VASU.G
[email protected]

STMS Route configuration in Three system Landscape with DEV,QA and PRD

Hi
We have Three system landscape.i.e DEV,Quality and PRD
Before Somebody configured the STMS by selecting standard two system land scape ( Dev and QAS)
We Have Installed Production Server And Added into Existing STMS Configuration
Now Three Systems Showing, In Import Overviw Screen
How Can I Create Route Between Three systems
What I am Asking Is Without Delet Old Roots
Can i Create it are Not
regards
NSN

Refer these links:
http://help.sap.com/saphelp_erp2005/helpdata/en/1c/2ddc0901db11d284870000e8a57770/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/44/b4a0137acc11d1899e0000e829fbbd/frameset.htm
Regards,
Ravi

Restricting STMS

Hello,
Is there a possibility of restricitng STMS to a specific module?
Since the consultants who have implemented SAP in my company are now leaving & the configuration control is being taken over by my company's functional leads, so I want to restrict my functional leads to their modules only. I mean whatever activity they perform, it should be restricted to their module only. So restrciting them on STMS to their module related activities is my first requirement.
Will appreciate help.
Thank you.

Hi,
It is not possible to restrict authorization on function modules and note that some of the values that you transport might be used by cross functions also, and hence practically it is not possible.
However, you can control transports using the Project field. The below SAP help document helps you with more information on how you can achieve this:
http://help.sap.com/saphelp_sm32/helpdata/en/03/dcb6b6048711d3b42a00609419f767/frameset.htm
Regards,
Raghu

Password policy not allowing to reconfigure STMS

Hi Guru's,
I have done system copy by database restore method, in post activities I have mistakenly deleted STMS configuration on domain controller, now when I am trying to add production server in landscape.
the password policy is not allowing us to reconfigure STMS.
I have manually reset the TMSADM password with alphanumeric format on all three system in client 000 with user DDIC,but I was getting same error message,
After removing password policy on PRD server it allowed me to configure STMS for PRD server.
Is there other way to reconfigure STMS without removing policy?
policy parameter:
login/min_password_specials ==>1
login/min_password_digits ==>1
since i dont want to remove password policy to reconfigure STMS,
please suggest, alternative.
-Gokul Chitode

you may want to have a look at SAP Note 761637 - Login restrictions prevent TMSADM logon

How to add a new system in existing 3 system lanscape in stms

Hi,
we have 3 system in our STMS i.e Dev->Qua->Prod. now we have install one more quality system for business requirement and add the same saystem in stms.
now my query is that how we can add this new system in existing transport route so that transport request can be added automatically to import queue of both quality system once released from development system.

Hi Nadar,
It is possible, But not recommended. Better if you have solution like...
DEV-->QAS1-->QAS2-->PRD
But it is possible by using transport groups. There are lots of posts aleady regarding this.
Basis Stms Configuration Notes
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/4-system-landscape-stms-2712918
4-system landscape
STMS config for dual prod (w/ auto synch)
Thanks
Asad

QAS Refresh from PRD

Dear Bhudev/Guest,
I am Planning to refresh my Quality system from Production's Offline Database Backup. I have seen you a lot posts.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Refresh from Offline backup (AQC from APC)
Let's say AQC is quality and APC is production.
Pre-processing Activity:
Verifications:
1. Verify the last offline backup in the source system /oracle//sapbackup/back.log
2. Verify that both the source and target systems are at the same Oracle level (which is already the case between APC and AQC)
3. It is recommended that an off-line backup be taken of the target system before starting this process, in case of fall back.
4. Confirm there is enough space in the target (AQC) file systems to contain the data from the source system this is required as we may have to copy the files from Production to quality. /oracle/SID/sapdata* folders should be having little more space as compared to the source filesystem.
5. Check access to SAP* for APC (000 and 400) and also for AQC (000 and 400)
6. Check other passwords such as adm and ora
7. Server : User : ora > sqlplus u201C/ as sysdbau201D > alter database backup controlfile to trace > exit In /oracle/SID/saptrace/usertrace, the last trace (check the time) is the script for recreating the control file. You will need to edit it. Please rename the trace file to ld.sql and send the file to the target system /oracle/SID Edit the Script: vi ld.sql Delete or comment out all lines at the beginning of the file before STARTUP NOMOUNT which is kept. Change old controlfile creation statement at the beginnig of the controlfile: Old line: create controlfile reuse database NOresetlogs archivelog; change to New line: create controlfile set database resetlogs archivelog; replace all occurences of string by in each line where appears :g / / s / / /g example: :g/P10/s/P10/T21/g Delete the following lines a the end of the script: ; RECOVER DATABASE; ALTER SYSTEM ARCHIVE LOG ALL; ALTER DATABASE OPEN;
8. Get from the Prod system (APC) the .aff and backDPR.log and copy them on AQC. (/oracle//sapbackup) Copy the files to /instkits/SID/. And after we can go on target source server and copy them from /instkits/SID to the /oracle/SID/sapbackup/. With the good owner and permission
9. Lock all the users in client 400 except Basis and post system message. Target system data collection (On AQC -400):
1. SM59 Expand all the trees, print by choosing: ->System ->List ->Print i) Compare list to R/3 connections on source system. Record details for any that will need to be recreated on target system.
2. SCC4 Record all client settings. -> Tableview ->Print ->Standard List -> List -> Print Make sure you understand the columnsu2026
3. SE06 Record system change options
4. RZ10 Record the instance profile settings for: rdisp/wp-no-btc and rdisp/max_wprun_time
5. STMS Record current transport routes. ->Overview -> Transport Routes -> manually expand all trees -> system ->list ->print
6. Request customer to provide u201Ccatch-upu201D list of transports to be applied to system after refresh (QA and Sandbox systems).
7. RZ04 Record current work process set-up. Highlight each operation mode and click instances/op modes button. i) Print with ->System ->List ->Print
8. SAP License Ensure the SAP license information is available. If not on-hand, logon target system as adm and enter command: saplicense u2013show. This information is also available on OSS.
9. TSM Nodename View /usr/tivoli/tsm/client/api/bin64/dsm.sys on source and target system. Record the nodename entries. These will be SAP or server names.
11. Take printer Export through SPAD and save it locally to desktop->SPAD
12. Take Export of User Master from the client 400 through SCC8 target system is AQC , so that it may be re-imported through STMS. Note the Transport number here also verify the transport exist in the queue. DB Restore from offline backup from APC:
1. Stop SAP on AQC -> Login as aqcadm -> stopsap
2. Change the TSM node on AQC-> cd /usr/tivoli/tsm/client/api/bin64 ls -lrt vi /usr/tivoli/tsm/client/api/bin64/dsm.sys Change it to point to APC, comment the AQC Node. Post Restore Acitivity:
1. Stop Database Delete Old controlfile rm /oracle/AQC/sapdata1/system_1/cntrl/* rm /oracle/AQC/saparch/cntrl/* rm /oracle/AQC/origlogA/cntrl/*
2. Re-create the controlfile and then after that start the database User : ora > cd > sqlplus u201C/ as sysdbau201D > @ld.sql > alter database open resetlogs;
3. Change the sapr3 password Server : User : ora Temporarily, we have to change the sapr3 password to the default password. With SAPBA, change this user password to pass.
4. Test the connection: Server : User : adm > R3trans u2013d It should have a return code of 0000
5. Reasign tempfile alter tablespace psaptemp add tempfile '/oracle/AQC/sapdata1/temp_1/temp.data1' size 6020M reuse autoextend on next 20971520 maxsize 10000M; alter database rename global_name to AQC.WORLD; drop user OPS$APCADM cascade; drop user OPS$ORAAPC; create user OPS$ORAAQC identified externally default tablespace psapdnausr temporary tablespace psaptemp; grant connect, unlimited tablespace, SAPDBA to OPS$ORAAQC; grant connect, unlimited tablespace, SAPDBA to OPS$AQCADM;
7. Change the instance profile to stop all the background processing To be sure that no production batch are executing, set rdisp/wp_no_btc to 0 posprocessing:
8. Startsap
9. Run Transaction SICK (as sap*)
10. Installing license through the tcode: slicense While logged in as 000/sap/using password of APC system Get the License from service.sap.com and download it to local machine Log in 000 client using SAP and run the Tcode slicense import printers, run BDLS for logical system name conversions se06 posprocessing stms usermaster import import profiles for QAS
thanks
Bhudev
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Hi Pranav
why the SIDs of production and QAS are same, did you do refresh of QAS from PRD ?
If yes, then you should have done control file creation and change of SIDs, after the datbase restore...
however, if you want to create the new control file and change the SID then try to consider the following steps:
1. Login as orasid
2. connect to sqlplus
3. run query: alter database PRD backup controlfile to trace;
4. It will create a control file as a latest trace file (.trc) in the directory /oracle/PRD/saptrace/usertrace
note: logout of sqlplus
5. Rename that .trc file into ldQAS.sql
6. copy this file into /oracle/SID ie. /oracle/QAS directory
7. edit the .sql file as below
8. CREATE CONTROLFILE SET DATABASE u201CQASu201D RESETLOGS ARCHIVELOGS;
add above statement replacing the below:
CREATE CONTROLFILE REUSE DATABASE u201CQASu201D NORESETLOGS ARCHIVELOGS;
9. Replace all occurences of string <PRD_SAPsid> by <QAS_SAPsid> in each line where <source_SAPsid> appears
:g/PRD/s/PRD/QAS/g
10. login in sqlplus, stop database
11. as oraqas, delete old control files:
rm /oracle/SID/sapdata1/system_1/cntrl/*
rm /oracle/sid/saparch/cntrl/*
rm /oracle/SID/origlogA/cntrl/*
12. again login into sqlplus (as sysdba always)
13. run this .sql : @ldQAS.sql
note: it should give a message that control file creaated.
14. Open the database using: alter database open resetlogs;
15. alter database rename global_name to QAS.WORLD;
16. drop user OPS$PRDADM cascade;
17. drop user OPS$ORAPRD;
18. create user OPS$ORAQAS identified externally default tablespace <tablespacename>
temporary tablespace psaptemp;
19. grant connect, unlimited tablespace, SAPDBA to OPS$ORAQAS;
grant connect, unlimited tablespace, SAPDBA to OPS$QASADM;
at SAP level:
1. you can run BDLS to convert logicalsystems from PRD to QAS SID
Bhudev
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
In both post, There is some difference specially like User droping.
Whether I have to run BDLS or Drop usr and create or both activity have to be done?????
Regards
Dharmendra

Please explain step by step:-
7. Server : User : ora > sqlplus u201C/ as sysdbau201D > alter database backup controlfile to trace > exit
In /oracle/SID/saptrace/usertrace, the last trace (check the time) is the script for recreating the control file.
You will need to edit it. Please rename the trace file to ld.sql and send the file to the target system /oracle/SID
Edit the Script: vi ld.sql Delete or comment out all lines at the beginning of the file before STARTUP NOMOUNT which is kept.
Change old controlfile creation statement at the beginnig of the controlfile: Old line: create controlfile reuse database NOresetlogs archivelog; change to New line: create controlfile set database resetlogs archivelog; replace all occurences of string by in each line where appears :g / / s / / /g example: :g/P10/s/P10/T21/g Delete the following lines a the end of the script: ; RECOVER DATABASE; ALTER SYSTEM ARCHIVE LOG ALL; ALTER DATABASE OPEN;
8. Get from the Prod system (APC) the .aff and backDPR.log and copy them on AQC. (/oracle//sapbackup) Copy the files to /instkits/SID/. And after we can go on target source server and copy them from /instkits/SID to the /oracle/SID/sapbackup/. With the good owner and permission
Break into steps and explain. It looks confusing to me because I am new to ECC with Oracle.
Regards
Dharmendra

Same SID for QA & Prd systems - pros and cons?

We have the foll systems:
1. Enterprise Portal 7.0
2. NWDI 7.0
3. NW 7.0 (with XECO - Ecommerce)
4. TREX 7.1
5. Content Server 6.40
6. ECC 6.0
Currently the QA and Prd systems have the same SID and system/instance no, although they are on different hosts.
We would like to know what are the long term pros and cons for keeping the QA and Prd SIDs the same for all systems.
We are already making a list, so thought we might as well get more inputs from the community too.
We already have this arrangement for the past 3 months and have not faced any major issues.
A couple of cons though:
1. Cannot use solman as it cannot distinguish between the diff servers with same SID
2. ABAP transports from QA to Prd have to be manually done (cannot use STMS)
Thanks
Prasad

Hi Manoj,
Changing the SID of java systems is a very tedious procedure. Hom sys copy is just a part of the SID change...there are a whole lot of configs to be done after that...the task is eq to a new setup of systems
For once, the efforts put in are huge..you can see there are 5 systems..besides, it will involve coordination from all teams - basis, development, functional, project management.
Here are a few advantages that we know of:
1. No efforts reqd to change back to original SID
2. During disaster recovery, we just have to restore the production database on QA and change the hostname, whereas its not so in case of having diff SIDs
3. For end-users this will be transparent because they will be using the hostname in the URL which is anyways different
We have the same SIDs for the past 3 months and have not seen major issues, but we also would like to know from the long term perspective if there are any risks that we have not foreseen...hence we seek help from the community.
Hope its clear now
Thanks for your response
Prasad

STMS restriction in PRD

Similar Messages

Maybe you are looking for