ADS Error

Error:-  ADS: com.adobe.ProcessingException: No output was gener(200101) [or] Error creating PDEFont for font Utopia-BoldItalic 

We are unable to view or print of any requests in PDF format in our Production system and it throwing error "ADS: com.adobe.ProcessingException: No output was gener(200101)" [or] "Error creating PDEFont for font Utopia-BoldItalic". We have checked the ADS RFC connection, The ADS_AGENT user and ran the  FP_TEST_00 and all checked out ok

Solution: - 

For this case there two possibilites to fix the issue.

1. The issue is related to ADS and SAP being installed on a mounted drive with the 'cio' option. Re-mount the drive without the 'cio' option and this will solve the problem.

please find the below link for more info for 'cio' option.

and search for cio for a detailed description.

2. If the above is not the case, you need try to add font Utopia-BoldItalic
according to the below steps.

Adding Fonts 


Adobe document services require access to fonts that are installed with the Font Manager Module. This module contains a number of Adobe bundled fonts installed in /usr/sap/<SAPSID>/JC<xx>/j2ee/os_libs/adssap/FontManagerService/fonts/adobe.

Note: -  1) In an Application Server Java, enter JC<xx>.
            2) In an Application Server ABAP + Java, enter DVEBMGS<xx>.

Warning: - Do not change this directory or its content.

You can also add fonts obtained from other vendors. The types of fonts you can add are OpenType® (.otf), TrueType® (.ttf), and PostScript® Type 1 (.pfb/.pfm).


To add fonts:

     1.      Create a subdirectory called fonts below the /usr/sap/<SAPSID>/SYS/global/AdobeDocumentServices/FontManagerService directory.

     2.      Create a subdirectory called customer below the fonts/ directory created in the previous step.

     3.      Copy your fonts into the /usr/sap/<SID>/SYS/global/AdobeDocumentServices/FontManagerService/fonts/customerdirectory.

     4.      Ensure that the <sid>adm user has read+write permission for the directory /usr/sap/<SID>/SYS/global/AdobeDocumentServices/.

     5.      Restart the following services for the changes to take effect

  • Document Services Font Manager
  • XML Form Module 

If the above two cases will not work, you need to update the latest SP level for ADS

Additional Info

For any ADS error, before we need to check all the test case to get what exact the error.

Access transaction SE38 then run the reports bellow:

FP_TEST_IA_01 - test interactive forms
FP_TEST_00 - simple test
FP_PDF_TEST_00 - ADS Version Information
FP_CHECK_DESTINATION_SERVICE - check destination (twice. with the check
box marked and unmarked)

Kindly execute the test reports, as per note 944221

To Know ADS Support Package, please execute the below transactions.

http://<java_host>: <java_port>/sap/monitoring/ComponentInfo

BR* Tools

BR* Tools   

BR*Tools provides you with menus to perform a wide range of database administration functions for your database

BRTools (and BRSpace) is the successor of SAPDBA. SAPDBA is no longer delivered with WAS 6.40 (NetWeaver 04). You can continue to use SAPDBA 6.20 for Oracle 9.2 on SAP systems that are based on Web AS 6.40. However, SAP recommends that you only use the BR*Tools there. You can of course also use the SQLPLUS command tool.


BRTOOLS is the program that displays the menus from which the other BR programs are called.

Not all functionality of SAPDBA is included in the new BR*Tools. P.e. the “Alter table or index parameters” and “Reorganize tablespace and data files” are missing. 

Overview of the tools

BR*Tools User Interface

The user interface to BR*Tools provides you with menus to perform a wide range of database administration functions for your Oracle database. The menus are controlled by BRTOOLS, which in turn calls one of the functional BR programs.

You can use BR*Tools with a:

  •  Character-based interface
  •  GUI

Character-based interface

Character-based interface, as in the following example, which shows the main menu:

BR0280I Time stamp 2003-03-06 11.30.57
BR0656I Choice menu 1 - please make a selection
BR*Tools main menu
  1 = Instance management
 2 - Space management
 3 - Segment management
 4 - Backup and database copy
 5 - Restore and recovery
 6 - Check and verification
 7 - Database statistics
 8 - Additional functions
 9 - Exit program
 Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:


BRGUI is the graphical interface for BR*Tools. It displays output and gathers user input for BR*Tools


This SAP tool for the Oracle database enables you to back up database files.
The smallest unit that can be saved with BRBACKUP is a file. You can use BRBACKUP for backing up both files in the database and non-database files and directories.

 Use the backup_mode from the Initialization Profile init<DBSID>.sap or the command option brbackup -m|-mode for this purpose

This parameter is used by BRBACKUP to determine the scope of the backup activity.
Syntax: backup_mode = all|all_data|full|incr|<tablespace>|<file_ID>|<file_ID1>-<file_ID2>|<generic_path>|sap_dir|ora_dir|<object_list>
Default: all


This SAP tool for the Oracle database enables you to archive offline redo log files.
  • You can also start BRARCHIVE when the database is shut down. 
  • You should archive the offline redo log files on tape using BRARCHIVE. 
  • In contrast to BRBACKUP, BRARCHIVE does not have its own management of tape continuation.  When a tape is full, you must restart BRARCHIVE to write to the next volume.

Logging for BRARCHIVE 

BRARCHIVE writes the following file system logs:

·<SAPDATA_HOME>/saparch/a<encoded timestamp>.<ext>
Every detail log contains information about the actions performed during an archiving run.
This summary log contains a brief entry for every archiving operation that was performed.

BRARCHIVE also records its actions in the database tables SDBAH and SDBAD


This SAP tool enables you to restore an entire database backup or parts of it, when the backup was performed with BRBACKUP. Any non-database files and directories you saved can also be restored.  In the process, the subdirectories in sapdata<n>directories are automatically created, when necessary.

You can also restore the offline redo log files that were backed up with BRARCHIVE.  This operation can be performed at the same time as the restore of the corresponding backup.

Ø·BRRESTORE can run unattended when option -c force is set. The option -c only suppresses the first confirmation prompts for mounting a volume.


·BRRESTORE uses the BRBACKUP logs and the summary log from BRARCHIVE to decide where to restore the requested file.  You can manually specify a different directory as well.

·One or more incomplete BRRESTORE runs can be completed with the option -f. BRRESTORE automatically determines the files to be restored.


The SAP tool BRRECOVER for Oracle databases is used as a database administration tool to help you recover your database. 

You can use BRRECOVER to perform the following:

  • Complete database recovery 
  • Database point-in-time (PIT) recovery 
  • Tablespace point-in-time (PIT) recovery 
  • Whole database reset 
  • Restore of individual backup files 
  • Restore and application of offline redo log files 
  • Disaster recovery 


The SAP tool BRCONNECT for Oracle databases is used as: 

· A database administration tool, which you can call yourself from the command line

· A utility tool, which BRBACKUP calls in the background

BRCONNECT is specially designed to administer multi-schema databases, in which you have more than one SAP System in the same Oracle database

  • Database System Check with BRCONNECT  
  • Adapt Next Extents with BRCONNECT 
  • Update Statistics with BRCONNECT  
  • Changing Database User Passwords with BRCONNECT  
  • Clean Up Old Logs and Trace Files with BRCONNECT  

BRCONNECT cleans up the following files:
  • Detailed BRARCHIVE logs in the saparch directory 
  • Detailed BRBACKUP logs in the sapbackup directory 
  • Detailed BRCONNECT logs in the sapcheck directory 
  • Detailed BRRESTOE logs in the sapbackup directory 
  • Detailed BRSPACE logs in the sapreorg directory 
  • BRBACKUP disk backups of the database files 
  • BRARCHIVE disk backups of the offline redo log files 
  • BRSPACE export dump and export script directories 
  • Oracle trace and audit files 
  • Log records in the SDBAH and SDBAD tables 
  • Log records in the XDBtables 
  • Database check results in DBMSGORAtable


* Instance management
    - Start up database
    - Shut down database
    - Alter database instance
    - Alter database parameters
    - Show instance status
    - Show database parameters
* Space management

  ----------- ----------------
     - Extend tablespace
     - Create tablespace
     - Drop tablespace
     - Alter tablespace
     - Alter data file
     - Move data file
     - Show tablespaces
     - Show data files
     - Show redolog files
     - Show control files
     - Show diska volumes
* Segment management 

- Reorganize tables (online)
- Rebuild indexes (online)
- Export tables
- Import tables
- Alter tables
- Alter indexes
- Show tables
- Show indexes
- Show table partitions
- Show index partitions
- Show segments
- Show segment extents
- Show free extents

Checking BR*Tools Release Information 

pat2036:oras94 4> brtools –V | brspace -V
BR0651I BRTOOLS 6.40 (40)
 Patch   Date     Info
 36  2006-01-11  Small functional enhancements in BR*Tools (note 914174)
 38  2006-03-29  BR*Tools support for MDM databases (note 936665)
 40  2006-08-30  Wrong message numbers in BR*Tools 6.40 (note 976755)
release note              680046
kernel release            640
patch date                 2006-08-30
patch level                 40
make platform             rs6000_64
make mode                 OCI_920
make date                  Sep  5 2006

Summary of the Tools

BRBACKUP - Backs up data files, conrol files, and online redo log files of the database.

BRARCHIVE - Backs up offline redo log files

BRRESTORE - Restores data files, control files, and redo log files

BRRECOVER - Recovers database files and restores profiles and log files

BRSPACE - Manages the database instance, space, and segments (that is,   tables and indexes)

BRCONNECT - Performs database administration tasks such as statistics update, check database system, adapt next extents, clean up logs and DBA tables.  Functions as a help tool to monitor the database during a backup

BRTOOLS - Displays the menus from which the other BR programs are called. Functions as an internal help tool started by BRBACKUP, BRARCHIVE, and BRRESTORE.

BRGUI - Functions as a Java-based GUI, working as the front-end display program for BR*Tools

Initialization Profile

BR* Tools uses the initialization profile init<SID>.sap as a input file.
The following are the important parameters in the init<SID>.sap file
  • exp_dump_dir 
  • exp_table 
  • Imp_table 
  • rebuild_index 
  • reorg_table 
  • show_period 
  • space_copy_dir 

This parameter specifies the directory of the export dump file                                
Syntax : exp_dump_dir = < directory name >
Default : $SAPDATA_HOME/sapreorg

This parameter specifies the table for an export
Syntax: exp_table = [<owner>.]<table> | (<table_list>)
Default : None
exp_table= (SDBAH, SAPR3.SDBAH)

This parameter specifies the table for an import
Syntax: imp_table = [<owner>.]<table> | (<table_list>)
Default : None
imp_table= (SDBAH, SAPR3.SDBAH)

This parameter specifies the database indexes for an index rebuild
Syntax: rebuild_index = [<owner>.]<index> | (<index_list>)
Default : None
rebuild_index= (SDBAH`0, SAPR3.SDBAH`0)

This parameter specifies the table for reorganization
Syntax: reorg_table = [<owner>.]<table> | (<table_list>)
Default : None
reorg_table= (SDBAH, SAPR3.SDBAH)

This parameter specifies the time period for which BRTOOLS display log files
Syntax : show_period = <days>
Default : 30
Possible values :
0 – Show all available log files
1 – Show logs created today
>1 – Show logs files created in the previous specified number of days

This parameter specifies the directory for file copies during space management.
Syntax : space_copy_dir = <directory name>
Default : $SAPDATA_HOME/sapreorg

Logs for BR*Tools 

Logs are created for BRBACKUP, BRARCHIVE, BRRESTORE, BRRECOVER, BRCONNECT, and BRSPACE. These supply information about database operations and are useful for problem analysis.
The following types of logs are written:
  •  File System Logs
  •  Database Logs in tables SDBAH and SDBAD

File System Logs 

For more information, see:

·        BRBACKUP Logs
         Detail log - b<encoded timestamp>.<ext> ( eg:  bdvecswx.anf )
         Summary log - back<DBSID>.log (eg: backS94.log )
Directory : /oracle/<SID>/sapbackup

·        BRARCHIVE Logs
        Detail log - a<encoded timestamp>.<ext> (eg: aduryokf.svd )
        Summary log - arch<DBSID>.log (eg: archS94.log )
Directory : /oracle/<SID>/saparch

·        BRRESTORE Logs
         Detail log - r<encoded timestamp>.<ext> (eg: rdvecswx.rsb )
         Summary log - rest<DBSID>.log  ( eg: restS94.log )
Directory : /oracle/<SID>/sapbackup

        BRRECOVER Logs
      Detail log - v<encoded timestamp>.<ext>
      Summary log - recov<DBSID>.log ( eg: recovS94.log )
Directory : /oracle/<SID>/saparch

·        BRSPACE Logs
       Detail log - s<encoded timestamp>.<ext> ( eg: sduvytan.tse )
       Summary log - space<DBSID>.log (eg: spaceS94.log )
Directory : /oracle/<SID>/sapreorg

·        BRCONNECT Logs
        Detail log - c<encoded timestamp>.<ext> (eg: cduxtdrn.chk)
        Summary log - conn<DBSID>.log ( eg: connS94.log )
Directory : /oracle/<SID>/sapcheck

Database Logs

The database logs of BRBACKUP, BRARCHIVE, and BRCONNECT are stored in tables SDBAH and SDBAD

This table contains information that refers to the backup as a whole:

·        Starting time of the backup or BRCONNECT processing
·        End time of the backup or BRCONNECT processing
·        BRBACKUP/BRARCHIVE/BRCONNECT action ID (encoded   timestamp of the file system log names)
·        BRBACKUP/BRARCHIVE/BRCONNECT function ID (extension of the file system log names)

This table contains information that refers to the backup of one file:
     File name
·        Oracle file ID or log group number
·        End time of the backup of the file
·        Name of the volume where the file was saved
·        Position of the file on the volume
·        Backup ID of the external backup program
·        Compression rate of the software compression
In addition, table SDBAD contains internal BRBACKUP information about compression rates and backup durations for the individual database files.
For BRCONNECT, SDBAD tables contain information on the total number of objects processed by BRCONNECT.

APO - LiveCache Administration

SAP APO-Live Cache Administration

TCODE LC10 is used for all LC operation using the SAPGUI

  • Properties -> Select Files Tab , These files are for Debugging issues, reviewing logs.
  • Current Status -> review current config, memory – No changes can be made. This is only for review.
  • Problem Analysis -> Allows for performance monitoring, view Messages and Logs.
  • Administration -> used for Operation of LC and Configuration. Configuration is where changes can be made to current parameters.

LC Operation
  • Start/Stop LC using LC10

  1. Login into the APO target system Tcode LC10 -> “livecache:Monitoring”
  2. Administration -> Operating Click Start LiveCache  or Stop LiveCache

  • Monitor usage for Data Area, Log Area and Cache
                    LCA -> Memory Areas

LC10--> Administration

  • Administration -> Configuration –Volumes


  • Enter the size in KB
  • Ensure there is enough disk space available on the FS
  • Type : File

Note : One datafile per FS is recommended for optimal performance


  • Confirmation .. Click “yes”

Coniguration – Modifying Parameters

  • Administration -> Configuration -> Parameters
  • General and Extended Tab have various LC parameters that can be modified
  • LC should be restarted for the changes in parameters to take effect
  • Using LC10 -> Configurtaion -> Backup 
  • Backup Medium can be defined , modified or renamed.

DBMGUI for Administration

LC Operation
  • Using DBMGUI– use one of the radio buttons to start, stop or set “admin” mode
  • It is not recommended to start Livecache using DBMGUI

Information Tab 

  • gives info about data, log areas used
  • Backup History
  • Current parameters set

Configuration using DBMGUI

  • In the configuration tab -> select parameters to modify, add parameter values
  • LC has to be restarted for new values to take effect

DBMGUI –Configuration -> Volumes

Adding Volumes -> Right Click on Available DataVolume Name -> Select New Volume

Ensure space is available on Unix FS and “sdb” user_id has write permission

LiveCache Checks

  • Use Tcode /n/sapapo/om00 – This displays a list of /sapapo/… Trasactions
  • Use /n/sapapo/om03 to test connectivity between LC and LC Database . This takes about 15 min to run



  • Click Back Arrow 

  • Review the output page. Last lines look as follows..


  • Various tabs provide information of various checks for Livecache. Review the tabs
  • Versions – > LC version, COM routines version, etc.
  • Checks -> Reports being run, parameter settings, etc
  • Error Messages -- Reads the knldiag.err file


  • Click on Consistency Check

  • Check all except “Production Campaigns”


  • Correct any inconsistencies if exists

Consistency Checks Programs

In se38, Execute Report

/SAPAPO/TS_LCM_CONS_CHECK –Consistency Check for existing time Series Network
  • Select Planning area– There are nine planning areas and only one can be selected for each execution
  • UnCheck “CHECK SNP Master Data”
  • While executing a “Repair” Planning Area should be Locked

In se38, Execute Report

/SAPAPO/TS_LCM_REORG—Check LC Time series Master Data
  • There is only one Planning Version and is always 000 
  • Click on Variants – 2 variants are defined, LC_CHECK and LC_REPAIR
  • Execute LC_CHECK – If it returns any Superfluous objects then execute LC_REPAIR to fix the problem.
  • Execute LC_CHCEK again to ensure no superfluous objects exist
NOTE : when LC_REPAIR is selected, Lock Planning Version and Repair boxes are checked.

Very slow start of the j2ee engine on AIX with 64bit IBM JDK

Very slow start of the j2ee engine on AIX with 64bit IBM JDK


  • Start of the j2ee engine on AIX with 64-bit IBM jdk is very long (more than 1/2 hour), a lot of services time out. Thread dumps of the server node show one or two running threads which are executing some method of the class Inet6AddressImpl like:




or other methods of the class Inet6AddressImpl.
  • "Java processes of instance Y35/JC00 [Java: UNKNOWN] did not reach state PARTRUNNING after 20:40 minutes. Giving up." message occurs during Installation.

Other terms
Inet6AddressImpl IPv6 IPv4 AIX 64-bit IBM JDK
Reason and Prerequisites
The reason is that the engine needs to run with Internet protocol version 4 (IPv4), but the IBM 64-bit JDK for AIX, v1.4 uses the IPv6 extensions to the TCP/IP protocol by default.
I. Change server node's settings

Add to the server node JVM settings the following parameter:

and restart the engine.

II. Change SDM node's settings

If the deployment via SDM is also slow you should add this parameter to the SDM JVM properties. To do so you have to edit 2 files:
1. All SPs:
In /usr/sap/<SID>/<instanceID>/SDM/program/config/
Replace the line



2.1.NW04 SP18 and lower or NW04s SP9 and lower:

In /usr/sap/<SID>/<instanceID>/SDM/program/
Change the line

sdm_com="$sdm_com -jar '/usr/sap/<SID>/<instanceID>/SDM/program/bin/SDM.jar'"


sdm_com="$sdm_com -jar '/usr/sap/<SID>/<instanceID>/SDM/program/bin/SDM.jar'"
(It must be on one line)

2.2. NW04 SP19 and newer or NW04s SP10 and newer:

In the file /usr/sap/<SID>/<instanceID>/SDM/program/
replace the line


with the line
III. Change dispatcher node's settings

Add to the dispatcher node JVM settings the following parameter:

and restart the engine.

For more info please review the SAP Note - Note 861333 - Very slow start of the j2ee engine on AIX with 64bit IBM JDK

SAP JVM 4.1 parameters NetWeaver 2004 and 7.0

SAP JVM 4.1 parameters NetWeaver 2004 and 7.0


This note describes recommended SAP JVM 4.1 settings for SAP NetWeaver 2004 and SAP NetWeaver 7.0.

Reason and Prerequisites
With SAP JVM 4.1, customers can get as long support for their JDK as they get for the remaining SAP NetWeaver 2004 and SAP NetWeaver 7.0 based software from SAP. SAP JVM 4.1 is supported directly by SAP.


In the following we describe two sets of JVM parameters: One set for the server nodes and one for dispatcher nodes of an SAP NetWeaver Application Server Java. The server node parameter set distinguishes parameters for 64 bit, 32 bit and parameters independent thereof.

The parameter sets described below target a typical SAP NetWeaver Application Server Java installation. Individual modifications might be applied, e.g. for the Java heap size.

    1. General remark on the Maximum Heap Size
              The maximum heap size is usually specified in the field "Max heap size (in MB)" in the Configtool. Therefore it is not needed to set it explicitly using the '-Xmx' option mentioned in following sections. If specified by '-Xmx', it will overrule any other setting. There is no preferred way to specify the maximum heap size. Both will lead to the same result.

    2. Server Nodes
              For server nodes you will need the architecture independent parameters plus either the 32 bit parameter set (for Windows on x86 or Linux on x86) or the 64 bit parameter set (for all other platforms).

    a) Architecture independent parameters
                       The following parameters apply for 32 and 64 bit platforms.
Remark: The Concurrent Mark & Sweep Garbage Collector is the recommended GC for all platforms
Remark: Mentioned only for completeness. Can be omitted, since it is set by default in the SAP JVM
Remark: Mentioned only for completeness. Can be omitted, since it is set by default in the SAP JVM
Remark: There is no "=" missing. A dot is used as separator instead. Please write all in one line without separating spaces. The parameter name is just broken down for readability.
Remark: This parameter will enable the GC history and to always look for the .hotspot_compiler file in JAVA_HOME instead of the current working directory.
      b) Additional parameters for 32 bit platforms
                       The followng additional parameters apply for Windows/x86 and Linux/x86.
    c) Additional parameters for 64 bit platforms
Remark: If larger values were already used prior to the JDK switch, they should be retained
Remark: If larger values were already used prior to the JDK switch, they should be retained
Remark: If you increase the total heap size (Xmx) you can increase the MaxNewSize in a proportional manner if necessary
Remark: If you increase the total heap size (Xmx) you can increase the NewSize in a proportional manner if necessary
    3. Dispatcher Nodes
              For the dispatcher nodes all platforms can use the same parameter settings described below. If the instance contains more than three server nodes we recommend to add 50MB of heap for each additional server node.
    a) Architecture independent parameters
Remark: This parameter will enable the GC history and to always look for the .hotspot_compiler file in JAVA_HOME instead of the current working directory.
    b) Additional parameters for 32 bit platforms
    c) Additional parameters for 64 bit platforms

For more information please review the SAP Note - Note 1603093 - SAP JVM 4.1 parameters NetWeaver 2004 and 7.0

My Blog List

About this blog

About Me