I have received complaint  from many users that short dump "DBIF_RSQL_SQL_ERROR" error occured in BI (i.e. BW) Quality system.

The error was "ORA-26040 data Block was Loaded using the NOLOGGING option".

This type of error  occurred only in BW system.   The problem occurred in BW Quality system after system refresh using restore / recovery Oracle database from BW Production system.

Tx code ST22

Execute brtool in ora<sid> to verify whether error occured pertaining to nologging.

Select  “6” – Check and verification

Select “1) Database System check

After Check database was completed, then view the check log file as shown in the figure below

As shown above ORA-01578 oracle data block corruption error was shown.  Normally block corruption is often due to a hardware error and there is a likely trace file or log entry that was created when it happened..

Open the trace file

I was  greatly relieved  that  from the trace file as shown in the above figure  the error ORA-26040 block corruption  was  the result of  NOLOGGING option.

The ORA-26040 error says that the “index”  was loaded using the “nologging” option and then possibly recovered from a backup before the nologging load.

The nologging option is a great way to speed-up inserts and index creation. It bypasses the writing of the  Primary Redo log, greatly improving performance .

However this approach is very dangerous if you need to roll-forward during this time period during a database recovery.

Therefore , before system refresh to BW Quality system, one must take a backup both before and after all nologging  operations.

It is not possible to roll-forward  through a point in time   since there are no images in the archived redo logs for this NOLOGGING operation. Hence full

backup  after performing any NOLOGGING operation is must.  Unfortunately  database backup team was not aware whether NOLOGGING was enabled for

some of the BW objects .

In SAP BW systems, ‘nologging’ for index creation from SAP level  is the default.

Indexes  for BW objects  “/BI*/F*” and “/BI*/E*”  are created with NOLOGGING . Hence drop only these indexes  “/BI*/F*” and “/BI*/E*”

The procedure for identifying the index name, partition table name  is described below

select segment_name,partition_name,segment_type ,block_id,blocks from dba_extents where (147445 between block_id and (block_id + blocks - 1)) and file_id=392 and rownum < 2

As shown above, the nologging was set on the creation of  index “/BIC/FGBIPC010~080”  for the given partition table name “/BIC/FGBIPC0100000000005”. Hence it is advisable to drop all the indexes  for the given partition table name rather than  dropping single  index  ““/BIC/FGBIPC010~080” .

The sql script to identify all the indexes for the given partition table name is as shown below

Then drop all the indexes associated with the given partition table as shown in the figure below.

Recreate the dropped indexes

The method to recreate the drop indexes can be done either using sql command  or ABAP report.

SAPLogin to  BW Quality system. Enter tx code se38 and report name “SAP_INFOCUBE_INDEXES_REPAIR "

Click execute (i.e. Press F8 key). New  screen appeared. Scroll down  continuously till you find green colour
highlighted as shown the figure below

Another method to to re-create the index using the following sql command

SQL> alter index  "<SAP-Schema>"."<index_name>"  rebuild partition "<SAP_SCHEMA>". "<partition_name>" online logging;

Execute brtool in ora<sid> to verify whether nologging  block corruption was cleared or not.

Select  “6” – Check and verification. Then Select “1"  Database System check

After Check database completed, then view the check log file as shown in the figure below

From the check log file,  nologging block corruption  for those  objects  was cleared i.e. ORA-01578 was not appearing in the check log file. This does not mean that the issue was resolved permanently. You need to execute database statistics and / or check database statistics frequently till no more error reported for other infocube objects.

Conclusion

• NOLOGGING option was enabled on couple of “/BI*/F*” and “/BI*/E*” objects in SAP BW production system. These are the infocubes objects. The indexes for these infocubes  objects had been created with “nologging”

• If you create an index with “nologging” option, Oracle database does not write the changes made to the index blocks to the online redologs. As a result the information is not written to the archive logs either.

• After restore to SAP Quality system during system refresh and apply recovery, many block corruption for infocube objects were reported  after executing brtools for database check or database statistics. That is an expected behaviour.

• Either drop or rebuild  all the infocubes indexes  immediately after system refresh and the error will be gone.

Best Practise  to prevent the NOLOGGING Block corruption after system  refresh from SAP BW Production to  SAP BW Quality

• Perform offline full database backup  in SAP BW production system– so no need to use recovery option  after restore to Quality system.

• In case offline database backup is not possible, then  use   online full database  backup both before and after all nologging  operations.

• NOLOGGING for index creation must be turned off with transaction code “SPRO” in BW production system. See the OSS note 1812719.

• SAP strongly recommend to perform database backup / restore / recovery  using  standard SAP BRbackup / BRrestore / BRrecovery tools .

• Use latest version and patch level  of BR*  tool  for your operating system. Brrestore and BRrecovery tool automatically repairs nologging indexes during brrecovery

• DO not use any other tool except SAP standard BR* tool.

FAQ

Question :  Why ORA-26040 data  block corruption  was not reported in SAP BW Production system after executing database check or database statistics  using brtool?

Ans: Because the SAP BW production system was never restored.  Incase if the SAP BW Production system crashed or or migration to new  hardware (Homogeneous System Migration), then data block corruption due to NOLOGGING on some tables  might be reported  in SAP  BW   Production  system  after restore and recovery  via incorrect version of brtools.

In this checklist which i have prepared just you have to export in excel replace SID by SID in your landscape and go ahead .Many of the changes can be done before restart . So please review and share you ideas on same .Please share your view on same !!

A general rule of thumb for good SAP Performance is that the application should make use of table indices, wherever available ('SQL/Index Agreement'), in order to ensure the most efficient access to the database. Despite the apparent simplicity of ABAP code being converted to SQL which executes in the database, DB2's Cost Based Optimizer (CBO) actually considers a number of factors in determining exactly how it will access the database.

About The Cost Based Optimizer

• The CBO considers the SQL that is passed to DB2 from the application, as well as statistics about the table and its indices from the DB2 Catalog
• DB2 Catalog statistics are generated by the DB2 'runstats' utility, which populates the catalog with values for cluster-ratio, cardinality, etc.
• Depending upon the catalog statistics, and the internal algorithms of the DB2 Optimizer, DB2 may choose an access path which differs from 'SQL/Index Agreement'

SQL/Where-Clause Agreement

What Are The Impacts Of Access Path Problems?

Many times they are characterized by a database read 'jumping the tracks' from an indexed to a sequential read, which can manifest itself as an order of magnitude increase in run time

Degradation is at the SQL level - relative infrequency of an SQL statement within a program can mitigate or mask negative effect on overall transaction

On Update statements, degraded access path leads to longer held locks, table contention, and an increase in deadlocks and timeouts when executed in parallel with other statements requiring the same table

How Can We Detect Access Path Problems?

Customer complaint of drastic performance degradation for a specific program or transaction

Trace of long-running SQL during system monitoring (SM66, ST05)

Analysis of most resource-intensive SQL statements in cursor cache (ST04 Transaction for DB2 z/OS systems)

Following any of the above, you determine:

Explain of SQL statement yields an access path which does not match the index corresponding to the 'where clause', AND Performance of SQL statement is worse than previous benchmark

Verification Of Access Path Problems

Trace and 'explain' long-running SQL

Use ST05 to trace specific user id, program or process (and drill-down and explain the suspect SQL), OR

Use ST04>>Thread Activity, in order to view SQL and explain for a particular process ID (PID)

Check the 'access path' from explain for agreement with fields of 'where clause'

Access path should show sequential read, indexed read, etc

If access path and where clause are not in agreement, check for other available indices in DB02 to see if there is a better match for the where clause

If there is a better match for the where clause, compare the statistics in DB02 for both indices (actual access path and expected access path, to try and determine the delta)

NOTE: In some cases, notably for 'small' tables, the DB2 Optimizer will opt for a sequential read or full table scan even when a full index key is provided. This is because for such tables, it is actually more efficient for DB2 to scan the entire table/ tablespace than to use the index.  (This is a potential pitfall, however, if you have a very small table grow to be very big over a short period of time, with no execution of Runstats to 'inform' DB2 of the change --  this will likely result in bad response time)

Root Causes Of Access Path Problems

Bad/Inefficient SQL

Code only makes use of partial keys for available indexes, lessening the likelihood that the CBO will choose the desired access path

Use of database joins/views, particularly for large and/or volatile tables (if tables, for instance, grow to require reorg, joins can 'break', causing the SQL to scan the product of the tables, leading to ugly and exponential increases)

Poor index design

Key fields are duplicated among several indexes, giving them similar statistics and characteristics, and creating opportunity for 'index competition'

The key fields chosen do not provide sufficient selectivity to make the index a good choice

Need for maintenance (reorgs, runstats) of tables and/or indices

Data Skew -- SQL is written to match key, however, due to the nature of the data in the table, the index is not selective

Coding alone cannot resolve this problem. This potentially requires DB2 Hints, changes to index and/or changes to statistics

'Fixing' Access Path Problems

When 'fixing' these problems, we tend to go down a path from least to most invasive change.

These items assume that access path problem has been positively identified; verification is required after each of the following actions:

Have DBA execute runstats for the suspect index or table

Reorg the table and/or index if flagged by system, or if there has been significant and uncharacteristic activity on the table (excessive growth, mass deletions, data conversions, etc)

Analyze indexes to determine overlap/competition, dropping unneeded ones

Make changes to ABAP code, if possible/necessary:

Provide additional or all keys for desired index and ensure order of keys matches desired index

'Code-around' to avoid select, if it isn't critical

'Fake-out' Optimizer, through manual adjustment of certain catalog stats

Scan table for presence of data skew

Implement DB2 Hints in ABAP code to bias optimizer toward desired index for SQL

Introduction

Steps to change the SAP IMAGE on the right hand column of the screen:

Steps

Transaction code - SMW0

Select Binary data for WebRFC application

Hit Enter

Click Execute

Select ‘ZSTART_IMG’ and Click on ‘Import’ Button.

Specify the filename where your GIF file is located

Click on Local Object

Select the desired image.

Dear All,

Today i am going to create my first Document on scn community.Hope this document will be helpful for SAP experts also.

Purpose of creation of document is to install certificate on IE browser.Yesterday i searched one discussion over scn sso certificate not installed windows 8.1   

For the solution i also searched lot over service marketplace & on search engines also and provided some solution but every time users getting same issue i.e

Use Automatically select the certificate store based on the type of certificate.

Choose Next to proceed.

Finally click on Finish to get

and dear friends now you can get certificate as like i got under certificates tab

After all these steps you all will be able to logon through IE ,without getting any ActiveX error .

Hope this document will help experts in future as a resolution for this type of issue with IE browser.

Thanks to all for encouraging me to write this document.

Best Regards,

Gaurav Rana

Table Partitioning – What is this ?

Table partitioning is a data organization scheme in which table data is divided across multiple storage objects, called partitions.

Partition by Range (PBR)

We can specify a range for each data partition when we create a partitioned table. A partitioned table uses a data organization scheme in which table data is divided across multiple data partitions according to the values of the table partitioning key columns of the table. The ranges specified for each data partition can be generated automatically or manually.

Partition-by-growth (PBG) table spaces let you partition according to data growth, which enables segmented tables to be partitioned as they grow, without the need for key ranges. These are best used when a table is expected to exceed 64 GB and does not have a suitable partitioning key for the table. DB2 manages PBG table spaces and automatically adds a new partition when more space is needed to satisfy an insert. The table space begins as a single-partition table space and automatically grows, as needed, as more partitions are added to accommodate data growth.

Table Partitioning – Why is this needed?

No Table in DB2 V9 can grow more than 64GB – DB2 Limitation.

Once Table reaches 64 GB – No more Data inserts are possible.

Due to high data volumes and limited Short Term Data Archiving opportunities for Business data.

Proactively identify and mitigate issues at early point in the life cycle to reduce outage and issues later.

Will take less time now – when tables are smaller.

Requires downtime – Based on the current size of the table.

Partition Options :

Partition By Range

Require extensive data analysis to define the limit keys

All Indexes can be partitioned.

Too Many Partitions – will hamper Index performance – unless Indexes are properly used.

Requires Downtime to convert Tables to Partition by Range

If all indexes are also partitioned – DBA can Reorg one partition at a time

Partition By Growth

Less upfront Analysis is needed

Indexes cannot be partitioned.

Requires Downtime to convert Tables to Partition by Growth

This is a default option from SAP BASIS 7.20.

Once Table grows really big , the table can never be Reorged and can only be Runstated.

T Code SE14 is used to check details of tablespace and partition details.

Created by  : Brindavan Mookaiah

Designation : SAP BASIS Consultant

          ADS connection from PPM system to Portal 7.3

SAP ADS connection from PPM5.0 to Portal 7.3

Pre-requisite steps

AS JAVA

AS ABAP

Step by step

As java

1. 1)      Deploy ADS in java………………………………………………………………………………………………………
2. 2)      Create ADSUSER……………………………………………………………………………………………………….
3. 3)      Check ADS services…………………………………………………………………………………………………….
4. 4)      Create RFC in SOA from JAVA to ABAP systems................………………………………………………….......

AS ABAP

1. 1)      Create ADS_AGENT user………………………………………………………………………………………..
2. 2)      Activate services in SICF…………………………………………………………………………………………
3. 3)      Create PDF printer…………………………………………………………………………………………………
4. 4)      Create RFC connection from ABAP to JAVA systems. ……………………………………………………....
5. 5)      Test connection ……………………………………………………………………………………………………

Issues and troubleshooting …………………………………………………………………………………………………..

1. 1)      Deploy ADS

                     Adobe Document Services (ADS) comes installed by default with NetWeaver AS Java and is SAP’s standard way of creating PDFs by SAP applications. These PDFs can be normal PDFs or interactive (called Adobe Interactive Forms). The SAP system using ADS can be any NetWeaver ABAP or Java system

Note: If ADS is not in JAVA than deploy through telnet or JSPM

Reference link: -Http://wiki.scn.sap.com/wiki/display/TechTSG/(JSTSG)(Telnet)DeployController+Commands?original_fqdn=wiki.sdn.sap.com

1. 2)      Create ADSUSER

               Create ADSUSER with assigned the role SAP_ADSCALLER   in Java system

           Check in “http://<server>:Port/irj/portal

3) Check ADS services : http://<server>:Port/nwa

      Operations --> Systems --> Start & Stop

4) 1) Create RFC connection to from ABAP to JAVA systems : http://<server>:Port/nwa

Create Destination FP_ICF_DATA_<SID of As ABAP> in SOA.

Go to nwa (http://<server>:<port>/nwa)

1. Go to SOA --> Technical Configuration-->Select Destinations

   Click create 

Enter Destination Name as FP_ICF_DATA_<SID of As ABAP>Select Destination Type as HTTP. Click Next. Enter URL of As ABAP system (http://<server>:<port>) e.g. http://<servername>.com:8000

Enter System ID and Client of As ABAP system. Click Next

  Select Authentication as Basic. Enter User as ADS_AGENT and its password.

Click on Finish.

As ABAP

Login to As ABAP system.

1) Create user ADS_AGENT as a system user in transaction SU01 and assign roles SAP_BC_FP_ICF, SAP_BC_FPADS_ICF & SAP_BC_JSF_COMMUNICATION.

Note: Either assign standard roles or make a copy of this role to Z roles. If you are assigning standard roles then make sure that profile of these roles should be generated.

2) Create role ADSCALLERS in PFCG and assign user ADSUSER to it.

3) Activate services in SICF

Go to T_cpde SICF and click excute

Activate below services

/default_host/sap/bc/fp

/default_host/sap/bc/fpads   

Create RFC connection to from ABAP to JAVA systems

Go to t-code SM59 and create ADS RFC as Type G.

a) In Target System settings, enter target host name and Service no. of your As Java systems.

b) In Path Prefix, enter- /AdobeDocumentServices/Config?style=rpc

c) In Logon & Security tab, select Basic Authentication. Then, enter user adsuser and its password

Save and click connection test

Configuration Check for PDF-Based Forms in ABAP

For test this report you need LOCL or PDF1 printer to check. if you dont have PDF1 printer then create the same in T-code SPAD.

Login into ABAP system and  executed the below report in T-code SE38.

1. 1)   FP_PDF_TEST_00

1. 1)   FP_TEST_00

Issue and trouble shooting

Ads connection issue with report “FP_TEST_00”

Error:

“ADS: com.adobe.ProcessingException:

Solution

1) Stop the JAVA system

2) Login into  JAVA system at OS level and go to the folder like below

  " /usr/sap/SID/J00/j2ee/os_libs"

then  rename the file  "adssap" "adssap.org"

portal system need to start again and the file adssap will generate automatically.

Issue has been resolved.

For more help for issue and trouble explained in SAP NOTE: 944221 - Error analysis for problems in form processing.

Oracle records database changes in its redo logs.

When Data Guard is activated, these changes are shipped from the primary to the standby and applied there.

This keeps the two databases synchronized with a time lag dependent on how often the changes are shipped and how long it takes to ship them.

ODG Standby Database Types

Physical Standby

• Identical to primary
• Updated via redo apply

Logical Standby

• Can be different structure to primary
• Updated via sql statements               

ODG – Available Modes

Mode

     =Maximum protection (LGWR, SYNC, AFFIRM)

               highest level of protection

               no data loss

               primary stops if redo data cannot be applied to the standby

     =Maximum availability (LGWR, SYNC, AFFIRM)

               high level of protection

               minimal data loss

               switches to maximum performance mode if standby unavailable

               automated catch-up of gaps if redo was not able to be written

     =Maximum performance (LGWR|ARCH, SYNC|ASYNC, AFFIRM|NOAFFIRM)

              medium level of protection

              some data loss

              primary not affected by standby unavailability

General objectives of DR system :

• Reduce recovery time in case of a disaster

                    Recovery Point Objective (RPO) = no more than X minutes of data loss

                    Recovery Time Objective (RTO) = Y hours from declaration of disaster

                    where X and Y are chosen by Project Build Team

• Reduce dependence on tapes

                    With tape based DR, tapes need to be shipped to DR site. Tapes can be lost or damaged with problems identified too late. ODG will know when a   redo log is missing or damaged at the point when it is to be applied to the standby not when the disaster has already occurred.

ODG Implementation Overview :

• Build Standby DB
• Setup network connection between primary and DR
• Refresh Standby with data from Primary DB (ship tapes or rsync over network)
• Synchronize databases (primary shutdown & apply redo logs or final rsync with primary in backup mode)
• Activate Oracle Data Guard
• Monitor (alert logs, network, primary db performance)
• Initial test - bring up standby to validate system

Configure required parameters on Primary and Secondary DB in init<SID>.ora or spfile as per Oracle online documentation - Data Guard

Concepts and Administration.

ODG Activation Overview

Once all ODG parameters are set, on the PRIMARY DB:

sqlplus / as sysdba

SQL> alter system set log_archive_dest_state_2=‘ENABLE';

SQL> show parameter log_archive_dest_state_2

Deactivate via:

sqlplus / as sysdba

SQL> alter system set log_archive_dest_state_2=‘DEFER';

SQL> show parameter log_archive_dest_state_2

ODG Troubleshooting

• Manual Monitoring options

          Database alert logs

          ST04N

• Automated Monitoring

          Alerts from OS level

          Solution Manger

          Oracle tools

Database alert logs

Oracle Alert Logs can be found in $SAPDATA_HOME/saptrace/background on both Primary database and Standby database.View the logs to check for messages / errors:

• more alert_<SID>.log | grep <ORA- / error / archival / GAP>
• tail –f alert_<SID>.log
• less alert_<SID>.log

Standby Database Backups

• Place the DB in read only mode
• Take a file system backup
• Place the DB back into managed recovery mode
• Clean up old redo logs after 2 successful backups

Disaster Recovery: High Level Overview

ODG Support: Common Problems

The following problems can occur :

• Missing logs
• Logs not being applied
• Cannot allocate new log
• Redo log storage filesystem full / filling

Problem: logs missing / not received

Problem: Redo logs not being applied

Problem: Can not allocate log

Problem: Redo storage full / filling

At first in the beginning the EWA report only reported the standard CPU data for the physical server and the data for this is directly collected by SAPOSCOL in a 24 hour buffer in which for each hour 4 times 60 measurements are stored because SAPOSCOL collects the data every 15 seconds by default.

After this SAP decided to create new monitor structures for the OS virtualization but the monitoring data for the CPU_Virtualization_Power

is not stored in the 24 hour SAPOSCOL buffer anymore. Actually the data is still collected by SAPOSCOL but only as a snapshot and we do need the

CCMS monitoring segment to store the data for a longer period. This can be done by using an ABAP report which reads the SAPOSCOL snapshot

data and stores the data in the CCMS monitor segment but this report only can be started each 5 minutes or this can be done by using a SAPCCM4X

agent and the agent can read the SAPOSCOL snapshot data every 60 seconds and sometimes even a little bit faster than this.

Now, if you do not use the SAPCCM4X agent then the difference between the old EWA report and the new one is 240 measurements or 12 measurement each hour.

If you are using the SAPCCM4X agent the number of measurements each hour will be at least 60. I know that this is still not the 240

measurements which we had before but at least it is much better then the 12 measurements.

Perhaps, in the further SAP can try to change something in the agent and collect the last 4 SAPOSCOL snapshots (if available) and in this way we also will get 240 measurements in the CCMS monitor segment each hour again.

-How to use SAP transaction ST06 for SAP performance analysis

http://www.sap-perf.ca/sap-st06-for-performance-analysis/

Annual SAP Security audit has always been a tough ask for administrators.

to extract the Combination of critical authorization & monitor the same is a time taking exercise but it can be extracted on a simple click with SAP Critical Authorization Reports all you have to do is maintain the critical Authorizations.

to maintain the critical authorizations execute the transaction SU_VCUSRVAR_CHANGE

1)  Double Click Critical Authorizations

2)  Click on New Entry you can also Copy it from Standard depending upon your requirement.

     Select the Color based on criticality

3) after adding your entries select the newly created Authorization ID and Double click the Authorization Data on Left Pane

Under Object mention the Authorization objects field Name enter the Field name For e.g

Save the entries

4) Double Click Variants for critical Authorization

and maintain the Variant by Clicking New Entries Save the New Entry

and then Select the newly created entry & double click the Critical Authorization

and add the critical authorization which we created in Step 2

now execute the transaction S_BCE_68002111

select the created variant and execute the report

Dear All,

Today i am going to create my first Document on scn community.Hope this document will be helpful for SAP experts also.

Purpose of creation of document is to install certificate on IE browser.Yesterday i searched one discussion over scn sso certificate not installed windows 8.1   

For the solution i also searched lot over service marketplace & on search engines also and provided some solution but every time users getting same issue i.e

Use Automatically select the certificate store based on the type of certificate.

Choose Next to proceed.

Finally click on Finish to get

and dear friends now you can get certificate as like i got under certificates tab

After all these steps you all will be able to logon through IE ,without getting any ActiveX error .

Hope this document will help experts in future as a resolution for this type of issue with IE browser.

Thanks to all for encouraging me to write this document.

Best Regards,

Gaurav Rana

Created by  : Brindavan Mookaiah

Designation : SAP BASIS Consultant

          ADS connection from PPM system to Portal 7.3

SAP ADS connection from PPM5.0 to Portal 7.3

Pre-requisite steps

AS JAVA

AS ABAP

Step by step

As java

1. 1)      Deploy ADS in java………………………………………………………………………………………………………
2. 2)      Create ADSUSER……………………………………………………………………………………………………….
3. 3)      Check ADS services…………………………………………………………………………………………………….
4. 4)      Create RFC in SOA from JAVA to ABAP systems................………………………………………………….......

AS ABAP

1. 1)      Create ADS_AGENT user………………………………………………………………………………………..
2. 2)      Activate services in SICF…………………………………………………………………………………………
3. 3)      Create PDF printer…………………………………………………………………………………………………
4. 4)      Create RFC connection from ABAP to JAVA systems. ……………………………………………………....
5. 5)      Test connection ……………………………………………………………………………………………………

Issues and troubleshooting …………………………………………………………………………………………………..

1. 1)      Deploy ADS

                     Adobe Document Services (ADS) comes installed by default with NetWeaver AS Java and is SAP’s standard way of creating PDFs by SAP applications. These PDFs can be normal PDFs or interactive (called Adobe Interactive Forms). The SAP system using ADS can be any NetWeaver ABAP or Java system

Note: If ADS is not in JAVA than deploy through telnet or JSPM

Reference link: -Http://wiki.scn.sap.com/wiki/display/TechTSG/(JSTSG)(Telnet)DeployController+Commands?original_fqdn=wiki.sdn.sap.com

1. 2)      Create ADSUSER

               Create ADSUSER with assigned the role SAP_ADSCALLER   in Java system

           Check in “http://<server>:Port/irj/portal

3) Check ADS services : http://<server>:Port/nwa

      Operations --> Systems --> Start & Stop

4) 1) Create RFC connection to from ABAP to JAVA systems : http://<server>:Port/nwa

Create Destination FP_ICF_DATA_<SID of As ABAP> in SOA.

Go to nwa (http://<server>:<port>/nwa)

1. Go to SOA --> Technical Configuration-->Select Destinations

   Click create 

Enter Destination Name as FP_ICF_DATA_<SID of As ABAP>Select Destination Type as HTTP. Click Next. Enter URL of As ABAP system (http://<server>:<port>) e.g. http://<servername>.com:8000

Enter System ID and Client of As ABAP system. Click Next

  Select Authentication as Basic. Enter User as ADS_AGENT and its password.

Click on Finish.

As ABAP

Login to As ABAP system.

1) Create user ADS_AGENT as a system user in transaction SU01 and assign roles SAP_BC_FP_ICF, SAP_BC_FPADS_ICF & SAP_BC_JSF_COMMUNICATION.

Note: Either assign standard roles or make a copy of this role to Z roles. If you are assigning standard roles then make sure that profile of these roles should be generated.

2) Create role ADSCALLERS in PFCG and assign user ADSUSER to it.

3) Activate services in SICF

Go to T_cpde SICF and click excute

Activate below services

/default_host/sap/bc/fp

/default_host/sap/bc/fpads   

Create RFC connection to from ABAP to JAVA systems

Go to t-code SM59 and create ADS RFC as Type G.

a) In Target System settings, enter target host name and Service no. of your As Java systems.

b) In Path Prefix, enter- /AdobeDocumentServices/Config?style=rpc

c) In Logon & Security tab, select Basic Authentication. Then, enter user adsuser and its password

Save and click connection test

Configuration Check for PDF-Based Forms in ABAP

For test this report you need LOCL or PDF1 printer to check. if you dont have PDF1 printer then create the same in T-code SPAD.

Login into ABAP system and  executed the below report in T-code SE38.

1. 1)   FP_PDF_TEST_00

1. 1)   FP_TEST_00

Issue and trouble shooting

Ads connection issue with report “FP_TEST_00”

Error:

“ADS: com.adobe.ProcessingException:

Solution

1) Stop the JAVA system

2) Login into  JAVA system at OS level and go to the folder like below

  " /usr/sap/SID/J00/j2ee/os_libs"

then  rename the file  "adssap" "adssap.org"

portal system need to start again and the file adssap will generate automatically.

Issue has been resolved.

For more help for issue and trouble explained in SAP NOTE: 944221 - Error analysis for problems in form processing.

Purpose

The purpose of this document is help in searching for specific content (relating to an error log) in the SAP Netweaver Application Server ABAP workprocess (or any other R/3 related service/process) traces. This can be a very tedious affair if many workprocesses are configured and this document explains how to do this from the SAP server end, rather than logging to the operating system to search in the actual trace file.

Example Scenario

Lets say the configured Single Sign On (SSO) setup between SAP Portal and the R/3 system fails with issues similar to:

Usually in such cases, the BASIS admin analyzes the J2EE and ABAP server logs. Now from the J2EE end, more details can be seen from the diagtool trace ( see http://service.sap.com/sap/support/notes/1045019 for SAP NW 6.40 and 7.00 servers and http://service.sap.com/sap/support/notes/1332726 for SAP NW 7.1+ servers), but when it comes to the ABAP server, the request can be handled by any one of the R/3 dialog workprocesses (usually one productive ABAP instance has 20 or more dialog workprocesses). Now searching all the dev_w0 files can be a cumbersome affair particularly if many ABAP instances are involved.


Solution

Use the ABAP server search function (TCode: /nSM51).

Type in the search text entry. There are some recurring error entries like “note 1055856” , “cannot create SAP logon ticket”, “TWPSSO2ACL”, “ticket issuer not trusted” etc. when there is an SSO issue. Or just use the user ID with which the issue was reproduced (or time or any other valid parameter).

The next screen shows you the exact trace file which has the error:

Navigate to the trace file (using /nAL11 or /nST11) and voila, you get more information:

Now, check the note and help documents to solve this. The only caveat is that this search is instance specific; if you have more than one ABAP server, this needs to be done individually on each instance.

NOTE: http://service.sap.com/sap/support/notes/1769367 :  Issuer of SSO ticket is not authorized also provides important information on troubleshooting such issues.

For a similar guide on checking application logs on an Application server JAVA, check:

http://scn.sap.com/community/netweaver-administrator/blog/2014/11/17/how-to-check-logs-for-particular-j2ee-application-issue

Dear Admin,

All SAP products support MaxDB database. Content server must use MaxDB and liveCache must use maxdb if livecache is not on HANA

We have MaxDB experts sessions available from MaxDB website: SAP MaxDB: The SAP Database - Training

Big thanks for MaxDB developers, they make the sessions almost cover all the topics. I am sure you will gain a lot after watching them.

Whenever there is new session available, MaxDB developer will update the news to MaxDB SCN forum. So if you are interested in MaxDB or your company
has MaxDB installed, please follow MaxDB SCN SAP MaxDB

Best regards,
James

                                          SAP PI Monitoring System checks

Summary:-

This document contains the information about how the SAP BASIS consultant to monitoring & troubleshooting the issue in SAP PI system.

Author: Brindavan Mookaiah

Designation: SAP BASIS Consultant

Table of contents:-

1)  sever monitoring at OS level

2)  Connection check

3) Integration  engine check  & cache check

4) RWB & SPROXY check

1)  ABAP+JAVA server check at OS level

Log on at OS level and go to the directory /sapmnt/<SID>/profile directory (at UNIX level)

  $ jcmon pf=<SID>_DVEBMGS<XX>_<hostname>  Note this will work JAVA stack more than 7.1 version

  $Jsmon pf=<SID>_DVEBMGS<XX>_<hostname>   This will work in lower version.

The screen will appear below.

Then type 'P V' for process view and check all the server node is running or not. if any of the services is not running find the issue in trace file under " /work directories or default trace.

check all the server node are running fine at SAP level.

Got to the URL : http://<hostname>:5<xx>00/nwa 

Click Operation management -> "Systems" -> "Start & Stop

All the process are in running status and should be green like below.

Also check the Intergation Buldier screen is working or not

Go to  the SAP transaction SXMB_IFR  The belwo screen should appear

Note: I f the T-code throw some error and only the URL is working http://<hostname>:5<xx>00/dir  then

Check the Java connector and related parameter like gateway ...etc to resolve the issue

Now click  (Integration builder and Enterprise Service Builder) one at a time,and verify that tools are launching without any problem. -->If the tools are throwing error then Check the SLD connection is working fine or not.

2) Connection check

Log on to the ABAP system and execute  the transaction SLDCHECK. You should get a web browser opened with option to log in to SLD. Log in with Dialog user and see if the the SLD status is running by following the red box shown int the below screenshot.

Check the SLD is running or not. if the T-code 'SLDCHECK'  throw the error then fix the issue, mostly issue can be handled in RZ70.

Important RFC Connection check

RFC connection are very important for SAP PI functioning, below are the RFC destination you should T-code SM59

1.AI_RUNTIME_JCOSERVER

2.AI_VALIDATION_JCOSERVER

3.LCRSAPRFC (also checked via SLDCHECK)

4.SAPSLDAPI (also checked via SLDCHECK)

5.INTEGRATION_DIRECTORY_HMI

The first four RFC connection is TCP connection which can be check NWA in URL  http://<hostname>:5<xx>00/nwa

then  click  Configuration Management" ->"Infrastructure" ->"JCO RFC Provider"  the screen will appear like below.

check all the RFC connection should work

cache clearing

Go to following URL to launch NWA and go  to

http://<hostname>:5<xx>00/rwb  and then click

Component Monitoring " ->"choose ‘All’ from the drop down menu of the field “Component with Status”" ->press"”Display" -> press"Cache Connectivity Test".

now click "Start Test the screen like below

cache check in through ABAP stack

Login into the ABAP system and excute T-code 'SXI_CACHE'

Check for any error in red and clean the cache clearance .

Goto" -> "Adapter Engine Cache

Mapping Runtime

while selecting Integration Server > Mapping Runtime, the status some of the tests is not "green --> then Go the URL :  : http(s)://<hostname>:<port>/exchangeProfile and check the host names, port, user, and logon language under Exchange Profile > Connections.

Then do the test HTTP connection via: http(s)://<hostname>:<port>/run/rtc

4) RWB & SPROXY check

Run time workbench check

Go to the URL : http://<hostname>:5<xx>00/rwb  and check the required monitoring...

SPROXY check

Login into the ABAP system and execute the T-code SPROXY and click test button and check some report.

1. Click the reports , SPROX_CHECK_IFR_ADDRESS  and check the address are maintained.

2. Click the test reports SPROX_CHECK_HTTP_COMMUNICATION should give you the information that the communication is working.

3. Click the  test report SPROX_CHECK_IFR_RESPONSE should give you a following output.

When we first install a new ABAP system, one of the parameters required is the name of the transport host. The installation tool defaults to the host on which we are installing, and if this is the first system in the landscape, this is often the choice we make. As frequently the first system installed is the development, or DEV, system, it's very common for DEV to become the central transport host as well as the transport domain controller (setup almost immediately after installation when we first configure STMS, and not to be confused with a Windows Active Directory domain controller).

This is all well and good, but fast forward a few (or maybe quite a few) years, and inevitably the day arrives when we would like to migrate our systems onto shiny new hardware. The System Copy guide documents the process of moving our ABAP system quite well, but it doesn't go into much (or any) detail about moving our Transport Domain Controller, nor does it talk about moving our transport host.

The example below assumes a Windows host, but the procedure should be easily adaptable to other operating systems.

What is a Central Transport Host?

Put simply, this is the location of \usr\sap\trans. If, during installation, we specify the current host (i.e., the one on which we are running the installer) as the transport host, then the installer will create the trans folder and its various subfolders, along with the rest of the folder structure required for the installation. If we specify a different host, then the installer will not create the trans folder, but instead will (or might) create a system parameter that points to the other host.

\usr\sap\trans is the folder containing all of our exported (released) transport requests, configuration information for our transport domain (or landscape), logs of transport request exports and imports, and by default the EPS Inbox which is used by SPAM and SAINT for support packs, add-ons, etc.

In a typical scenario, each transport domain will have just one \usr\sap\trans folder, and all the systems in that domain will use that same central folder.

Setting up the New Transport Host

Having determined that we need to migrate the transport host, the first decision is where to put it. It does not actually have to be on an SAP system. It could, for instance, be in a shared network location accessible by all the SAP systems in the transport domain. Or, it could move with the DEV system to the new DEV host. This decision depends upon our needs, and there is no right or wrong answer for all scenarios.

Either way, I recommend migrating the transport host before migrating the DEV system (or whichever system in the domain we are migrating first). This will simplify things later, as then we generally only need specify the hostname of the new transport host during installation with SWPM of each new target system.

Create Folder Structure

This part is simple. On the target host, at the root of the selected drive or volume, create an empty folder called \usr, then subfolder \sap and further subfolder \trans.

If we follow general system installation recommendations, then we may install the Solution Manager Diagnostics Agent (SMD or DAA) on the host before installing anything else, and in this case the \usr\sap folder will already exist, and we should use that.

Make sure the drive has plenty of free space, enough to accommodate the files we're going to move into it, plus headroom for future transports and support packs.

Copy Files and Subfolders

Easy. Simply copy (or move) all of the subfolders and their contents from the source system \usr\sap\trans to the target system \usr\sap\trans. If our source system is not in use at this point (and it really shouldn't be), then rename the source trans folder to something like trans.bak to ensure that it doesn't give us a false positive during our testing for success later.

Create sapmnt Share

Share the folder \usr\sap (not \usr\sap\trans) as sapmnt. For now, give Administrators full control and everyone else no access.

Create SAP_LocalAdmin Group

On the target host, create the local group SAP_LocalAdmin, and add the Active Directory global groups SAP_<SID>_GlobalAdmin to it, where <SID> represents the System ID of each SAP system in our transport domain.

Grant SAP_LocalAdmin 'Full Control' to both the sapmnt share and the \usr\sap folder (and all subfolders, which should happen by default).

Test that these permissions are correct by logging on to one of the other SAP hosts as <sid>adm and then navigate to \\<new_trans_host>\sapmnt\trans, and create, read, and delete a test file.

SAPTRANSHOST and DIR_TRANS

Here is where the fun begins. Depending on how long ago we first installed our source SAP system, and how old the installer program (i.e., sapinst) was, we might find any number of locations where pointers to the transport directory exist. We need to find all of them, and in most cases delete them, so that there is only one.

There are essentially three variables or parameters of importance to us: SAPTRANSHOST, DIR_TRANS, and DIR_EPS_ROOT. Each of these could be set (or not) in the default or instance profiles of our SAP systems, or one of them (SAPTRANSHOST) may be set externally, as an environment variable or as a DNS (Domain Name System) alias.

DIR_EPS_ROOT defines the location of the EPS Inbox and other structures for SPAM and SAINT, and if not explicitly set it will be derived as \\<SAPTRANSHOST>\sapmnt\trans\EPS. Unless we have intentionally separated the EPS inbox from the transport folders, this parameter should be left unset, i.e. at the default. So, delete it wherever we find it.

Likewise, DIR_TRANS defines the location of the transport folder root, i.e. \usr\sap\trans, for STMS. This one is fairly commonly found set in instance profiles, but could also be in a default profile. If we use a central transport host and we stick to the default folder names, as described here, then there is no need to set this parameter. We should delete it wherever we find it.

Parameter Priority

DIR_TRANS is the parameter that STMS will use to find the transport folders. If both SAPTRANSHOST and DIR_TRANS are set in a profile, DIR_TRANS will take precedence in determination. If DIR_TRANS is not explicitly set, then the system will substitute standard values to calculate it as \\<SAPTRANSHOST>\sapmnt\trans.

Therefore, if we eliminate DIR_TRANS from all profiles, determination rests only upon a correct setting of SAPTRANSHOST. This becomes the key to simplifying our migration.

STMS is going to look first for DIR_TRANS to be explicitly set. If it doesn't find it, it will substitute as mentioned above using the value of SAPTRANSHOST. It will look first for SAPTRANSHOST in the local system's Instance Profile, and if not found there, then in the Default Profile. If it doesn't find it in any profile, it will look for it as an environment variable (for the user SAPService<SID> or <sid>adm) or via the operating system's hostname resolution.

SAPTRANSHOST

SAPTRANSHOST may be set as a parameter in the instance profile, the default profile, or as an alias in the hosts file or DNS. At various times installation programs and documentation have defaulted to or recommended different approaches.

DNS

If we have only a single transport domain, and we have ready access to manipulate our DNS (Domain Name System) server, then setting an 'alias' record in DNS for SAPTRANSHOST to point to the IP address of the central transport host may be the easiest option. This is a task usually managed by network operations staff and not SAP system administration staff, so we won't go into the procedure here. Also, for that reason, it may be simpler to not rely upon DNS for this parameter.

The other complication associated with setting SAPTRANSHOST in DNS is that we may have more than one transport domain, and possibly also more than one central transport host. This could be the case, for instance, if we have one transport domain for our ECC landscape, and another domain for our SRM landscape, and perhaps another for BW, etc.

Finally, a DNS alias ends up as the lowest priority for determination, as it will be overridden by any of the other methods that could be used.

HOSTS

An alternative to DNS is to maintain the alias in the local hosts file. This was very common with early ABAP (i.e. R/3) systems, so we must definitely check for this and correct it (or potentially eliminate it).

The hosts file is a repository of IP addresses and hostnames maintained in the local server's filesystem. This is a mechanism for name resolution that predates DNS. In the event of an entry in the hosts file that conflicts with an entry in DNS, the hosts entry will take priority (but only for name resolutions on the local host).

The file is located at C:\Windows\system32\drivers\etc\hosts. It is a simple ASCII text file that can be edited with Notepad.

Look for entries similar to:

192.168.0.1     hostname.domain.com     SAPTRANSHOST

Obviously, the IP address will likely be different. Here, we have two options. We can edit the line so that the IP address and hostname match our new central transport host, or we can simply delete the line (assuming we have a working DNS system so that the actual hostname will be resolved correctly, but this is usually the case).

If we don't find such a line, we can insert a new one with the correct information, or we can ignore it and leave it alone. After all, there is another option.

Default Profile

The next place to look is for the SAPTRANSHOST parameter to be set in either the Default or Instance Profile. If it is set as a DNS or HOSTS alias, then it may not be set in the profiles at all. Ideally it should only be set in one place or the other, not both. Currently, SWPM will configure this as a parameter in the Default Profile on installation, so this is the practice I recommend.

It should be set in only one place, so we are going to eliminate any SAPTRANSHOST alias from the hosts file and any parameter for this (or DIR_TRANS) in the Instance Profile, and ensure it is set correctly in the Default Profile.

Environment Variable

There is one other possible place where a misconfigured SAPTRANSHOST variable could cause us grief. It is rare, but we might find it set as an environment variable for the <sid>adm user. If so, we should eliminate it and rely instead on the Default Profile. This will be much easier to manage going forward.

Restart

Unfortunately, changing this parameter in the system profiles, or for that matter in the hosts file, requires a restart of the application to take effect. In the case of a change in the hosts file, it also requires a restart of the SAP service (which is a good idea generally, anyway, when restarting the system for profile parameter changes, as some parameters require this as well).

Yes, this means there will be a brief production downtime to get this into effect, so plan ahead.

TP at the OS Level

One possible advantage to setting SAPTRANSHOST as a DNS alias or environment variable could have been for use with the tp command when used outside the ABAP system from the server console's command prompt. It is rare these days to use tp instead of STMS, but there are occasions that call for it. The proper way to handle this, however, is to set TRANSDIR in the transport domain profile. This is done via STMS.

Logon to the transport domain controller (possibly the DEV system), and go into transaction STMS. Select System Overview, then double-click on the system that is the Controller (there is a small icon next to the System ID for the primary and backup controllers; hover over them with the mouse to see a pop-up text identifying them).

Select the Transport Tool tab. There we should see a parameter called TRANSDIR. If it is not correctly set, change to edit mode and correct it.

It should have the Global flag checked, and the value should be \\<central_transport_host>\sapmnt\trans.

Save changes and select Yes to distribute changes immediately.

Testing and Wrap-up

So, we have exhaustively and methodically ensured that SAPTRANSHOST is correctly set in the Default Profile of all systems in our transport domain, and that both it and DIR_TRANS are not set anywhere else. At this point, everything should be working, but let's double-check.

While still logged into STMS on the transport controller, back out to the System Overview, highlight all the systems in the list (click on the column header), then one after the other select SAP System... Check... Connection Test, then Transport Directory, then Transport Tool. We should see green checkmarks for all tests, and when we expand the test results we should see that the new transport host is being used.

Now select Display Transport Groups, then Check Transport Groups. If all is correct, we should see a grid of green lights.

Back out two steps and go into Transport Routes. Select Configuration... Check... Transport Routes and then Request Consistency... In All Systems. It's not really all that time-consuming, so select yes for the warning prompt.

Finally, back out one step and go into Import Overview. Select Refresh. After a bit we should a green status for each of our systems' import queues. Drilling into a queue should show any waiting requests, and import histories should be complete with logs.

If any of the above checks yields an error, then we will need to go to the system involved with the error and double-check that we have eliminated and corrected all parameters, variables, and aliases, and that the system has read/write access to the transport folder.

Here I am going to discuss some issue in ST03N data missing due to DST time switch. The issue is more known but the solution provided everywhere is very confusing and not very clear . The ST03N data is more important to client as well as for a Basis administrator to  determine the system performance .

1. First check  that the SAP standard job is running or not. SAP standard job name  ,"SAP_COLLECTOR_FOR_PERFMONITOR" should be running with DDIC user in 000  client. The JOB should be scheduled with one hour interval. There is a  SAP standard note 16083  describes the standard job that needs to be  scheduled properly.

2. Next we need to check that the report SWNC_CONFIG_TIMEPROFILE , and then check that SWNC time profile , it should be calculate all hours separately.

Check the point , calculate all hours separately and execute. It will calculate your all hours separately.

The results should be look like this,

3. After a Daylight Savings Time change or Time-zone change, not all data is collected in ST03 anymore.  You are also missing data in transaction
STAD.The root cause must be like ,The Operating System time  and the SAP system time (especially in client 000) are not the same.   Both the OS and the SAP    system time (client 000) must both be correct  and the same in order for the ST03 statistics to work correctly. For this issue , please do the step given below,

1. First, ensure that your OS time and time-zone is set correctly.
2. On the SAP system, check all of the following in client 000:
3. The 'System Time Zone' in transaction STZAC should be the same as your OS time-zone.
4. For USA and Canada, ensure that the note 919538 is implemented correctly.  This means you should have the following USA 2007 entry in transaction STZBC (again, client 000):

For doing this you must need to follow the SAP note 919538 , to enter the entry to see

STZBC .

This entry should be added in the table TTZDV , from SE16 . But before that make sure all the changes should be done in 000 client and the clientmust be open. To give the input in TTZDV table you need few details like  below field. he database table TTZDV contains  a list of variable summer time rules in column DSTRULE. The column YEARFROM contains a year number for every rule, saying in which year the  rule applies. The columns MONTHFROM, WEEKDFROM, WEEKDCFROM, TIMEFROM, MONTHTO, WEEKDTO, WEEKDCTO, and TIMETO contain the month, week, day, and  time for the beginning and end of summer time.Now you need to check the report TZCUSTHELP to check if everything is  setup correctly.  When you run the report (in client 000) you should see the line "System time zone seems to be correct".

The output of the report should be like this.When  all time-zone settings have been corrected, allow the collector (job  SAP_COLLECTOR_FOR_PERFMONITOR) to run for some time in order to collect and total the statistics again.  A full run of all collector jobs is 24 hours.Finally, check if the full 24 hours of data for the last complete days are collected:Important:

• A correct set of rules must contain all rules specified in TTZZ for the time difference between time zones and the UTC reference time in TTZR
  and all rules specified for summer time in TTZD. If the time difference between summer time and winter time in TTZD is not equal to 0, the
  respective summer time rule must be included in at least one of the tables TTZDF or TTZDV. While TTZDF contains fixed dates for the switch,
  the date in TTZDV is variable, because a day in a particular week of a month is specified. The system always checks TTZDF first for the summer
  time rule and then TTZDV.
• The database table TTZZ contains  a list of possible time zones in the column TZONE. The entries in the columns ZONERULE and DSTRULE refer to the rules for the time difference of the time zone to the UTC reference time in table TTZR and to the rules for summer time in the tables TTZD, TTZDF, and TTZDV.
• The column ZONERULE of the database table TTZR contains  a list of possible rules for the time difference between time zones and  the UTC reference time. The columns UTCDIFF and UTCSIGN contain the time differences to UTC and their signs, while ignoring summer time.

Next
Phase is to check that the SWNCMONIINDEX table , in this table the AGR_TZONE should be equal to the time zone you set for the system.

that AGR_TZONE you need to check in STZBD transaction with summer time zone rule as well.

The  time specified for the beginning of summer time in the tables TTZDF and  TTZDV identifies the time when the clock is put forward by the summer
time difference when the winter time ends. The first second of summer  time is the time you get when you add the summer time difference to the
specified time.

An composite SAP note is also there to find out the time zone related issue.

198411 - Current data and information about time zones

101726 - Incorrect times and time zone setting

Must
Remember: When you change all those settings in 000 client ,then you
should run the job SAP_COLLECTOR_FOR_PERFMONITOR atleat 24 hours to
collect the data in correct time zone.

Thanks and Regards,

Basis Administrator

Hi all,

Here I am going to discuss the IDoc monitoring with the help of Solution manager Technical monitoring. This guide will help you to define a proper way to create IDoc monitoring and defining the threshold with the help of solution manager.

As we all know that IDoc is a very important parts between data interchange between SAP system. So monitoring of IDoc will give you less amount of risk losing business information.

I have seen in many client that IDoc is being monitored but we don't know exactly at what situation what needs to be monitor. So here I am going to present a brief rigorous description of IDoc monitoring via Solution manager.

In systems with high IDoc volume (table EDIDC has 10 million or more entries), IDoc monitoring can result in high response times.

The latest version of the IDoc monitoring data provider supports optionally a delta mode. With "deltamode" active, only the number of IDocs that have been updated since last monitoring data collection are monitored instead of always taking into account all IDocs. This will drastically reduce runtime. Also monitoring functionality is improved as now IDoc monitoring alerts are only raised if new errors occurred since last monitoring run.

Please follow the steps below to use the new deltamode.

1. Ensure that the support pacakge of your SAP Solution Manager System is SP05 or higher.

2. Ensure that the coding corrections from SAP Note 1729771 (version>=29) are applied in the managed system.

3. Ensure that you apply the latest monitoring templates in SAP Solution Manager as explained in SAP Note 1690352.

4. Up to Solution Manager 7.1 SP8, 6 IDoc monitoring metrics are delivered by default:

a) Number of IDocs in error status

b) Number of IDocs in error status older than 2 hours

c) Number of IDocs in intermediate status

d) Number of IDocs in intermediate status older than 2 hours

e) Number of IDocs in intermediate status last 15 minutes

f) Number of IDocs in error status last 15 minutes

Please activate only the following metrics in the monitoring templates:

Number of IDocs in error status last 15 minutes and

Number of IDocs in intermediate status last 15 minutes.

The other default IDoc monitoring metrics do not support "DELTAMODE" and are only included to support backward compatibility. They should be deactivated in case of performance problems with IDoc monitoring data collection.

There is SAP standard way to define the IDoc monitoring via Solution manager. I am attaching the  SAP document here for as a referral.

This document contains information for LiveCache system copy part of an SCM7.0 system copy. In the previous 2 parts, we have completed ABAP system copy and opened the system. Now we restore LiveCache instance from source system to target system through MaxDB Database Studio.

LiveCache version of SCM system is 7.7.07 Build48. LiveCache is installed on the same Linux x86_64 server with ABAP SCM 7.0 part.

Related SAP Notes:

457425 - Homogene liveCache-Kopie mit Hilfe von Backup/Restore

632357 - Sicherung der Daten aus dem liveCache für SCM >= 4.0

To prevent some misunderstandings and increase readibility, I prepared 3 seperate documents for DB2 restore and LiveCache MaxDB restore.

This part contains sapinst steps from the beginning until the "exit to restore DB2". Second part contains DB2 restore (from Snapshot) steps and third part contains LiveCache system copy instructions.

For the first part, that contains system copy screenshots (until restore) and information, go to link: SCM 7.0 (with LiveCache) DB2 Linux system copy-Part1/3 (Until restore)

For the second part, that contains DB2 restore steps. go to link: SCM 7.0 (with LiveCache) DB2 Linux system copy-Part2/3 (DB2 restore)

• After finishing SCM ABAP DB2 restore (system copy), we can install LiveCache instance. Point the path like in the screenshot, in the screen of SWPM sapinst. Then enter LiveCache SID and master password:

• Provide LiveCache 7.7 DVD location:

• Provide LiveCache user details and other parameters like in the screenshots:

• Provide locations and sizes for your LiveCache MaxDB log and data volumes. You can check your source LiveCache configuration to be sure.

• After checking sapinst parameter summary screen, you can execute it. There are 5 steps to be completed:

• Download the latest LiveCache patch from SWDC and patch it with the following command like below:

root-> pwd

/tmp/LC_Update/lca700032_livecache-linux-64bit-x86_64-7_7_07_50

root-> ./SDBUPD -d <LiveCacheSID> -u control,PASSWORD

Livecache 7.7.07.50

• Open your MaxDB Database Studio and register your both source and target LiveCache MaxDB servers. Firstly prepare a backup of source system via Right click -> Administration Tasks -> Backup... Then move the backup file to your target system to restore. Execute restore like in the screenshots:

• Finally restart your LiveCache instance through LC10 from your ABAP System.

     My LC10 screen is like this now:

TROUBLESHOOTING

• During MaxDB recovery, I got the following error. The same error is also discussed in that SCN link:
• Can't start Database Instance after a recovery with error

To overcome this error, click to "Medium COM" button on left bottom corner and take a new backup from your source system with the block size mentioned in the error code:

-903 Host file I/O error 6,Data recovery failed 113,Open medium on /tmp/XXXX for READ failed Servertask Info: because Error in backup task occured Job 1 (Backup / Restore Medium Task) [executing] WaitingT140 Result=3700 Error in backup task occured, Error code 3700 "hostfile_error" 127,RTE header size 524288 instead of 65536 bytes on medium /xxxxxx .

Calculate block size to give, dividing the header size in the error code by 1024, to convert it to KB. For example in my case, there was an error code with the value 524288 and I divided it by 1024. 524288/1024 = 512KB . I gave this value to make a new source system MaxDB backup. Then restoring it went fine!

• In LC10 screen I had a warning "Instance ONLINE, but no SQL access possible" . Due to this error, LiveCache reports, jobs can not be executed. SCN link for similar error:

Cannot open SQL connection to liveCache LCA

Also you can check your WP Workprocess logs under /usr/sap/SID/DVEBMGSSN/work . You'll see this error there:

*** ERROR => different codepage: application=UNICODE, LVC=ASCII

I changed the DefaultCodePage like in the screenshot, from ASCII to UNICODE and restarted LiveCache. The error is lost.

• 1864995 - sql error -4025 when connecting from SCM to livecache

This document contains information about DB2 10.1 FP3 restore steps. DB2 restore has been executed from the latest snapshot of the source system. Source system is an SCM 7.0 based on NW7.01, running DB2 10.1 FP3 on Linux x86_64.

To prevent some misunderstandings and increase readibility, I prepared 3 seperate documents for DB2 restore and LiveCache MaxDB restore.

This part contains sapinst steps from the beginning until the "exit to restore DB2". Second part contains DB2 restore (from Snapshot) steps and third part contains LiveCache system copy instructions.

For the first part, that contains system copy screenshots (until restore) and information, go to link: SCM 7.0 (with LiveCache) DB2 Linux system copy-Part1/3 (Until restore)

For the third part, that contains LiveCache MaxDB restore screenshots and specific LC information, go to link : SCM 7.0 (with LiveCache) DB2 Linux system copy-Part3/3 (LiveCache restore)

Restore steps would possibly differ in your environment, since those steps change dependent to the landscape infrastructure, filesystem structure, directory structure and used softwares in backup&storage processes.

SSID, ssid : Refers to source system SID.

TSID, tsid : Refers to target system SID.

• 1.Prepare relocation script on source system. Then copy it to target system. It is used to "relocate" source DB files copied from snapshot, to target DB.

Source system :

Su - db2<tsid>

brdb6brt -bm 5 -replace TSID=SSID,db2<ssid>=db2<tsid>

Relocation Script:  ./TSID_NODE0000.scr

• 2.Create mount points and mount the source system snapshot filesystems under those mount points on target system.

Target system:

root-> mkdir /tmp/SNAP_sapdata

root-> mkdir /tmp/SNAP_db2<ssid>

root-> mount -t nfs XXXXX:/vol_XXX_source_dbdata/dbdata/db/db2/db2_source_sapdata /tmp/SNAP_sapdata

root-> mount -t nfs XXXXX:/vol_XXX_source_dbdata/dbdata/db/db2/db2_source_db2<ssid> /tmp/SNAP_db2<ssid>

• 3.Copy source system files from snapshot backup to target system directories:

root-> pwd

/tmp/SNAP_sapdata/.snapshot/snap-daily_DATE_OF_LATEST_SNAP

root-> date; cp -Ppr * /db2/<TSID>/sapdata/ ; date

root-> pwd

/tmp/SNAP_sapdata/.snapshot/snap-daily_DATE_OF_LATEST_SNAP

root-> cp -pPr * /db2/<TSID>/db2<tsid>/

• 4.Rename directories and adjust file authorizations according to the target system users:

root-> pwd

/db2/<TSID>/sapdata

root-> mv db2<ssid> db2<tsid>

root-> pwd

/db2/<TSID>/sapdata/db2<tsid>/NODE0000

root-> mv <SSID> <TSID>

root-> pwd

/db2/<TSID>/db2<tsid>

root-> chown -R db2<tsid>:db<tsid>adm NODE0000/

root-> pwd

/db2/<TSID>/sapdata

root-> chown -R db2<tsid>:db<tsid>adm db2<tsid>

• 5.After those adjustments, we can execute the script that we've already prepared in the first step. Script initialize the target DB.

targetHost:db2<tsid>> db2inidb <TSID> as mirror relocate using <SSID>_NODE0000.scr

Relocating database...

DBT1006N  The "/db2/<TSID>/sapdata1/db2<tsid>/NODE0000/<TSID>/T0000000/C0000000.CAT" file or device could not be opened.

Unable to relocate database, cannot continue.

This error comes up, if the target and source system filesystem-directory structures differ. To overcome this, I've created symbolic links:

root-> ln -s sapdata sapdata1

root-> ....

root-> ln -s sapdata sapdata16

targetHost:db2<tsid>> db2inidb <TSID> as mirror relocate using <SSID>_NODE0000.scr

Relocating database...

Files and control structures were changed successfully.

Database was catalogued successfully.

DBT1000I  The tool completed successfully.

Database relocation was successful.

DBT1000I  The tool completed successfully.

• 6.Copy your source system's DB2 archive logs to target system, to make rollforward your target DB. On target system preape a script (rollforward<TSID>.clp) including rollforward command. In our case we've made "end of logs" recovery but "point-in-time" recovery is also possible.

     Run the script and complete your rollforward process.

targetHost:db2<tsid>>  db2 -tvf rollforward<TSID>.clp

rollforward db <TSID> to end of logs and complete OVERFLOW LOG PATH(/tmp/Temporary_Space_for_Source_Archive_Logs/)

                                 Rollforward Status

Input database alias                   = <TSID>

Number of members have returned status = 1

Member ID                              = 0

Rollforward status                     = not pending

Next log file to be read               =

Log files processed                    = S000xxxx.LOG - S000yyyy.LOG

Last committed transaction             = date-06.09.36.000000 Local

DB20000I  The ROLLFORWARD command completed successfully.

• 7.Activate your target DB. This command starts to create online DB logs under your /db2/TSID/log_dir directory.

targetHost:db2<tsid> >db2 activate db <TSID>

DB20000I  The ACTIVATE DATABASE command completed successfully.

• 8.Grant authorizations on your target database.

su - <tsid>adm

db2 grant secadm on database to user db2<tsid>

db2 grant dbadm on database to user db2<tsid>

db2 grant dbadm on database to user <schema_owner>

db2 grant dbadm on database to user <schema_owner>

su - db2<tsid>

db2 grant secadm on database to user <tsid>adm

db2 grant dbadm on database to user <tsid>adm

db2 grant dbadm on database to user <schema_owner>

db2 grant dbadm on database to user <schema_owner>

• 9.Drop and recreate your SYSTOOLSTMPSPACE.

targetHost:db2<tsid> > db2 -tvf /tmp/SCRIPT.clp

drop tablespace "SYSTOOLSTMPSPACE"

DB20000I  The SQL command completed successfully.

drop tablespace "SYSTOOLSPACE"

DB20000I  The SQL command completed successfully.

CREATE USER TEMPORARY TABLESPACE "SYSTOOLSTMPSPACE" IN DATABASE PARTITION GROUP IBMCATGROUP PAGESIZE 16384 MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 2 PREFETCHSIZE AUTOMATIC BUFFERPOOL IBMDEFAULTBP OVERHEAD 7.500000 TRANSFERRATE 0.060000 FILE SYSTEM CACHING DROPPED TABLE RECOVERY OFF

DB20000I  The SQL command completed successfully.

CREATE LARGE TABLESPACE "SYSTOOLSPACE" IN DATABASE PARTITION GROUP IBMCATGROUP PAGESIZE 16384 MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 32 M MAXSIZE NONE EXTENTSIZE 2 PREFETCHSIZE AUTOMATIC BUFFERPOOL IBMDEFAULTBP OVERHEAD 7.500000 TRANSFERRATE 0.060000 NO FILE SYSTEM CACHING DROPPED TABLE RECOVERY OFF

DB20000I  The SQL command completed successfully.

• 10.Install DB2 licenses.

targetHost:db2<tsid> > db2licm -a db2ese_c.lic

targetHost:db2<tsid> > db2licm -l

• 11.Restart your target DB and try to connect to it. Check R3trans connectivity.

targetHost:db2<tsid> > db2stop force

targetHost:db2<tsid> > db2start

targetHost:db2<tsid> >db2 connect to <TSID>

   Database Connection Information

Database server        = DB2/LINUXX8664 10.1.3

SQL authorization ID   = DB2<TSID>

Local database alias   = <TSID>

targetHost:<tsid>adm > R3trans -d

This is R3trans version 6.23 (release 720 - 31.10.12 - 20:12:06).

unicode enabled version

R3trans finished (0000).

TROUBLESHOOTING:

• <SQL0727N An error occurred during implicit system action type "3".>

Under installation directory sapinst_instdir

root-> more last_command.out

SELECT 'CALL SYSPROC.ADMIN_TASK_REMOVE(''' || RTRIM(NAME) || ''',' || CASE WHEN END_TIME IS NULL THEN 'NULL' ELSE '''' || RTRIM(CAST (END_TIME AS char(40))) || '''' END || ');' FROM SYSTOOLS.ADMIN_TASK_LIST WHERE PROCEDURE_SCHEMA = 'SA

PTOOLS'

SQL0727N  An error occurred during implicit system action type "3".

Information returned for the error includes SQLCODE "-204", SQLSTATE "42704"

and message tokens "SYSTOOLS.ADMINTASKS". SQLSTATE=56098

SOLUTION

http://scn.sap.com/thread/2098004

db2 "drop view SYSTOOLS.ADMIN_TASK_LIST"

• SQL0556N  An attempt to revoke a privilege, security label,.....

REVOKE DBADM ON DATABASE from user <TSID>ADM

DB21034E  The command was processed as an SQL statement because it was not a

valid Command Line Processor command.  During SQL processing it returned:

SQL0556N  An attempt to revoke a privilege, security label, exemption, or role

from "<TSID>ADM" was denied because "<TSID>ADM" does not hold this privilege,

security label, exemption, or role.  SQLSTATE=42504

SOLUTION

db2 grant dbadm on database to user <tsid>adm