PI service users locked

PI service users comes default with the installation and exists along side the password within the client of Integration server and exchange profile.
They are utilized in the PI environment for dialog free communication between central components of Netweaver usage type PI and also between app servers and PI

Below are the roles assigned to them

Service User	Description	Assigned Role
PILSADMIN	User for the Change Management Server	SAP_XI_CMS_SERV_USER
PIREPUSER	User for the Enterprise Services Repository	SAP_XI_IR_SERV_USER_MAIN
PIDIRUSER	User for the Integration Directory	SAP_XI_ID_SERV_USER_MAIN
PILDUSER	User for the System Landscape Directory (SLD)	SAP_BC_AI_LANDSCAPE_DB_RFC
PIAPPLUSER	User for sender applications	SAP_XI_APPL_SERV_USER
PIRWBUSER	User for the Runtime Workbench	SAP_XI_RWB_SERV_USER_MAIN
PIAFUSER	User for the Advanced Adapter Engine	SAP_XI_AF_SERV_USER_MAIN
PIISUSER	User for the Integration Server	SAP_XI_IS_SERV_USER_MAIN
PIPPUSER	User for principal propagation	SAP_XI_APPL_SERV_USER

These users will be maintained in different connections and transactions. Inorder to change the passwords, we need to change them in all those connections and transactions.

There is a typical procedure to vary the passwords of those users provided by SAP.


We need to follow the procedure from below notes for changing the passwords supported your PI version.

999962 - PI 7.10 and higher: Change passwords of PI service users

2474153 - How to change passwords of PI service users in Java Only PI system

936093 - PI: Change to passwords of PI service users

721548 - XI 3.0: Changing the passwords of the XI service users

Owners and authorizations for BR*Tools

The following setup is essentail to call the BR*Tools with out any error, especially while using transaction DB13 or DBACOCKPIT:

(1) ora and adm groups on DB server have a search path on /sapmnt//exe.

(All br* are contained in this directory.)

ora belongs to the dba group,

adm belongs to the sapsys group,


(2) adm group on the DB server has the rhosts entry: "+ adm".


(3) The ops$adm Oracle user has to be created within the DB and should have the sapdba role (not DBA!) (refer SNote 134592 for more information about the role).


(4) brarchive, brbackup, and brconnect belongs to ora and should have authorization 4775:

-rwsrwxr-x ora sapsys ...


Reason:

Both the operating system (OS) user ora and the OS user adm (for example, from SAP R/3, transactions DB13 or DBACOCKPIT) must be able to call these tools. These tools require access authorization to the database directories and files also on the log directories (saparch,

sapbackup, sapcheck, and sapreorg) of the BR*Tools. To ensure that they will be executed by both ora and by adm, they need to belong to the user ora, and therefore the s-bit must be set.

(5) brrestore, brrecover, brspace, and brtools belongs to adm and should have authorization 755:

-rwxr-xr-x adm sapsys ...

Reason:

These tools could also be used only by OS user ora, but not by adm. This ensures that the user adm doesn't have write authorization for the log directories and thus cannot create any logs. For this, no s-bit is about , and it's not necessary to define an owner aside from the standard owner adm.

If the tools were started using adm, they might terminate immediately after the beginning thanks to the missing log authorization. However, the user ora can start the programs despite this and also has the specified authorization for the log directories.

Queues stay in status READY in SMQ2

Queues stay in status READY in SMQ2

If you observe a situation where many queues are in READY status, the following
situations can apply:

 1. A resource bottleneck with regard to RFC resources. Confirm with transaction
SARFC.

 2. Long DB loading times for RFC tables. If using Oracle, ensure that SAP Note
1020260 - Delivery of Oracle statistics is applied.

 3. To avoid overloading a system with RFC load, the QIN scheduler only reloads
LUWs from the queues after a certain amount of DIA WPs have finished their
work. This can lead to long waiting times in the queues as explained in SAP Note
1115861 - Behaviour of Inbound Scheduler after Resource Bottleneck. Since PI is
a non-user system, we recommend setting rfc/inb_sched_resource_threshold to 3.

 4. Additional overhead during this step occurs due to every message being blocked
during processing. This is no longer necessary and should be switched off by
setting the parameter LOCK_MESSAGE of category RUNTIME to 0 as per SAP Note 1058915.

Reorganizing Tables with BR*Tools

Use

BR*Tools can be used to reorganize tables online for Oracle database in SAP system.

Note

This article gives an overview on the procedure to reorganize a table with BR*Tools.

For more information on the approach to table reorganization, see:

· Reorganization

· Reorganization Case Study

You can perform the following types of reorganization:

· Reorganize tables online

· Check tables for reorganization

· Clean up tables after aborted reorganization

· Conversion of LONG and LONG RAW fields to CLOB or BLOB online in Oracle 10g or higher

· Stop reorganization (command-line mode only)

· Suspend reorganization (command-line mode only)

· Resume reorganization (command-line mode only)

For more information, see -f tbreorg.

Prerequisites

You cannot perform online reorganization for tables with LONG or LONG RAW fields but you'll convert them to CLOB or BLOB online. After this conversion, you'll reorganize all tables online. For more information, see SAP Note 646681.

Procedure

1. From the command line, start the procedure using BRGUI or BRTOOLS, or :

 BRGUI or BRTOOLS:

i. Choose Segment Management ® Reorganize tables.

BRGUI or BRTOOLS displays the menu BRSPACE options for reorganization of tables, where you specify the choices with which you call BRSPACE.

ii. Set the required options:

Note

If required, in Table names you'll enter the names of multiple tables. You can use wildcards. For more information, look in to “Selecting Objects“ in Segment Management with BR*Tools. You can also specify a list of tables to be processed with reorg_table in the initialization profile init.sap.

In Tablespace names and Table owner, you'll specify multiple objects but you can't use wildcards. BRSPACE processes all the tables within the specified tablespace name(s) or all tables belonging to the required table owner(s). But these entries and reorganization action entry are not mandatory.

iii. Choose Continue.

BRGUI or BRTOOLS prompts you to start BRSPACE.

iv. Choose Continue to start BRSPACE.

¡ Command line:

Enter at least the following command:

brspace –f tbreorg

You can go with additional parameters, including the table names, if required. we can see BRSPACE -f tbreorg for more information.

Note

Whichever way you begin the procedure – with BRGUI or BRTOOLS, or from the instruction – you'll use quick mode if you recognize the ultimate object names, in this case the table names. For more information, see How to Use BR*Tools.

BRSPACE starts and you see a message that has Start of BRSPACE processing. From now on, BRSPACE writes a detail log.

2. If you've got already entered the table names, continue with step 5 (quick mode).

Note

If you've got entered multiple tables, BRSPACE displays as confirmation an inventory of tables for reorganization. If you've got not already made a final selection, you'll make a variety from this list.

Continue with step 5 (quick mode).

BRSPACE displays the Table reorganization main menu.

3. Choose Reorganize tables.

BRSPACE displays the table list:

4. Select a table or multiple tables.

Example

These examples only apply for character mode inputs..

To choose the first three tables within the list, enter 1-3.

To choose the first and third tables, enter 1,3.

To choose the first three tables and therefore the fifth, enter 1-3,5.

To choose all tables, enter 0.

BRSPACE will show the  Options for reorganization of tables.

5. Set the required options:

Note

There is no SQL instruction here because the reorganization is performed in several steps by an Oracle package, which contains multiple procedures.

6. to start out processing with the chosen options, choose Continue.

Results

Check the results in the BRSPACE logs.

· The summary log space.logdisplays the return code.

· The detail log s.tbr displays the details.

For more information on the way to view the logs with BR*Tools, see Showing Logs and Profiles with BR*Tools.

The file ddl.sql is created in the subdirectory of the directory $SAPDATA_HOME/sapreorg if the option –d|-ddl is set to a value other than no. The file contains the Data Definition Language (DDL) statements used for the creation of interim tables during the reorganization. For more information, see Reorganization. If the –d|-ddl option is about to only, then only DDL statements are created and therefore the actual reorganization isn't performed

How to create background job server group

(Like for Logon group:SMLG,For RFC logon group:RZ12,Spool server group:SPAD)similarly we can create backgroung job server group:SM61

Tcode…..>SM61

Steps:-

1>.Create a background server group using the instances which are having strong resource (CPU/RAM)

2>.Schedule the business critical jobs during the Month-End in that background server group.

Advantage:-

1>.Business critical jobs will run smoothly without any resource issue.

2>.Good for background job capacity planning by defining the background job server group

Disadvantages of other Methods:-

1>.Sometimes If we don’t define the target server then a business critical background job may fail if it goes to a weak resource server.

2>.If we define the target server manually and if there are many business critical jobs to define the target server then  that is tedious task to find out and keep the track which server is not loaded heavily.

Might help the team for OLTP production systems for background job administration.

How to delete a scheduled job in SAP

To delete a job:

Go to Transaction SM37. choose a job (or jobs) from the Select Background Jobs window. In the Job Overview, mark the job or jobs you would like to delete by checking the box to the left of the job name. Choose Job --> Delete.

Deleting Jobs That Have Dependent Jobs:

If you delete a job that has got to be processed before another job are often started, the dependent job can not be started. The system will let os know of any such existing dependent, or successor, jobs. You'll then got to either reschedule or delete the dependent job.

If you are trying to release employment whose predecessor job was deleted, the system sets the status of the job to Planned. To start this job, you want to release it and specify the beginning conditions.

How to copy tables to another system using R3trans

If you would like copy some tables to a different system, you'll use R3trans. The steps are the following:

Create in the system source the file: export.ctl

Export

File = 'export.dat'

Client = 201

Select * from table

And within the system target create the file: import.ctl

Import

File = 'export.dat'

Client = 301

Then execute in the source systems:

R3trans export.ctl

This creates a file named export.dat, then copy this file to target system and execute within the target system:

R3trans import.ctl

This imports the table to the target system.PD.

You can check the SAP Note No. 1942

How to add default printer to user in SAP system

We can assign the printer as default printer to particular user in SAP.
This blog shows the procedure on the way to add it.

1.SU01 screen

Click on change icon

2.Users Menu -à defaults

Here we've to feature a printer thereto particular user

Under spool control there's a column with output device.

Here we have to add the printer to the user

And check output immediately

SAP SYSTEM : 

CLIENT : 

User ID : XXXXXX

Then click on save button

The below screen shows that we have no authorizations to user changes.