sapinst troubleshooting guide

8/11/2019 Sapinst Troubleshooting Guide

http://slidepdf.com/reader/full/sapinst-troubleshooting-guide 1/23

Troubleshootin Documentation

SAPSAPSAPSAPinstinstinstinst®®®®

TroubleshootingTroubleshootingTroubleshootingTroubleshooting

GuideGuideGuideGuide

V 1.10 (from 18th February 2002).).).).



© Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and

SQL Server ® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®,

RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are

registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM

are registered trademarks of IBM Corp.

UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks of

the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®,

WinFrame®, VideoFrame®, MultiWin® and other Citrix product names

referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business

Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,

Management Cockpit, mySAP, mySAP.com, and other SAP products

and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. MarketSet and Enterprise

Buyer are jointly owned trademarks of SAP Markets and Commerce

One. All other product and service names mentioned are the

trademarks of their respective owners.

Disclaimer

Some components of this product are based on Java™. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used

by SAP’s Support Services and may not be modified or altered in any

way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:

http://service.sap.com/sapinstfeedback

SAP AGSAP AGSAP AGSAP AGNeurottstraße 1669190 Walldorf GermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.comwww.sap.comwww.sap.comwww.sap.com



Typographic Conventions

Type Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLETEXT

Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded

by body text, for example,SELECT and INCLUDE.

Example text Screen output. This includesfile and directory names andtheir paths, messages,names of variables andparameters, source code aswell as names of installation,upgrade and database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactlyas they appear in thedocumentation.

<Exampletext>

Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE

TEXTKeys on the keyboard, for example, function keys (such as

F2) or the ENTER key

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax



SAPinst Troubleshooting Guide V 1.10

4 Februar/2002

Contents

1 HOW TO USE THIS DOCUMENTATION................................................. 6

2 IDENTIFYING ERRORS AND SOLVING PROBLEMS............................ 7

2.1 Continuing the Installation After Solving the Problem...................................................... 8

2.2 Known Symptoms, Errors, and Solutions ......................................................................... 102.2.1 When Starting SAPinst .................................................................................................. 11

2.2.2 When Performing the Installation.................................................................................. 13

3 RESTRICTIONS ..................................................................................... 17

4 TECHNICAL INFORMATION................................................................. 18

4.1 Important Files in the Installation Directory .................................................................... 18

4.1.1 Overview........................................................................................................................ 18

4.1.2 Important XML Files..................................................................................................... 19

4.1.3 Log Files ........................................................................................................................ 19

4.2 External Support Tools ....................................................................................................... 21

4.3 SAPinst Start-up Options.................................................................................................... 22

4.3.1 Command Overview...................................................................................................... 22

4.3.2 Command Options Overview ........................................................................................ 22




Februar/2002 5

Document History

SAPinst Troubleshooting GuideVersion

Important Changes

V 1.00 (30th

January 2002) First Version

V 1.10 (18th

February 2002) • Introducing new unique error message numbersto topic: Known Symptoms, Errors, and Solutions

• Adding error messages and solutions




6 Februar/2002

1 How to Use this DocumentationThis documentation provides troubleshooting information for the installation procedures withthe tool SAP Landscape Implementation Manager , known for short as "SAPinst."

It is meant to be an additional information source beside a component installation guide (for example a SAP BW Server or SAP ITS installation guide).

It provides the following information:

• What to do if an installation error occurs

• Solutions to already known errors.

• Restrictions of the tool

• Technical information

Although this documentation provides software component-specifictroubleshooting, you must also refer to further component-specifictroubleshooting guides and related SAP Notes, which may be referenced inthe relevant component installation guide.

We highly appreciate your feedback about SAPinst! You can enter your comments at: http://service.sap.com/sapinstfeedback

This documentation is updated as required to inform you about new conceptsand solutions for the installation process with SAPinst. You can also findupdates at: http://service.sap.com/sapinstfeedbackTo help you recognize updated versions more easily, the hyperlink to thisguide contains date and version information, for example(Version 1.10, updated 20/DEC/2001)

Sections of this Documentation

Section Summary

Identifying Errorsand SolvingProblems

Procedure for identifying errors and solving problems and how to continue theinstallation

Also provides known error situations with clearly defined error messages andpossible solutions.

Restrictions Known restrictions of the toolTechnicalInformation

Related Information that could be useful during a troubleshooting phase, suchas log file description, command options, external support tools, and so on.

http://service.sap.com/?







Februar/2002 7

2 Identifying Errors and SolvingProblems

This section tells you what to do if SAPinst stops the installation due to an error.

1. Check the file sapinst.log at <SAPinst_INSTDIR> for the message type ERROR .

You can view sapinst.log by choosing View log in the error dialog box that

is displayed during the installation. A log viewer dialog is then displayed with the following features:- Use the View menu to see messages of a single type only (for example, type

ERROR ).- Additionally, you can open other SAPinst-specific log files with File -> Open.

a. Go to the end of sapinst.log and search for the message type ERROR .

In most cases, you can find details about the error situation and the step that failed.There are also corresponding Phase and Transaction sections that might give youmore useful information. For more information on SAPinst log files, see Log Files [onpage 19].

If sapinst.log refers to other log files in the relevant sections, check these log files

too.

b. Check if the error is already known [on page 10].

If you can find a solution here, continue the installation after solving the problem [onpage 8]).

2. If it is an unknown error or you could not find a solution:

a. Try to find the reason for the error, for example by repeating the command on theoperating system level and checking if the return code gives more information.

b. Search for SAP Notes by using SAPNet - R/3 Frontend containing possible solutions.

3. If you have found a solution, continue the installation after solving the problem [on page8].

4. If you cannot find a solution:

a. Copy the following files from your installation directory <SAPinst_INSTDIR> to

sapserv<X>:

− keydb.xml

− sapinst_dev.log

− Additional log file(s), if sapinst.log references those file in the error message.

For more information on using sapserv<X>, see SAP Note 40024.

b. Inform SAP via SAP Net - R/3 Frontend using the component BC-INS.

You can also create a customer message via SAP Service Marketplace at:http://service.sap.com/message

We provide you with a solution to your problem.

c. When you have implemented our solution, you continue the installation [on page 8]).




8 Februar/2002

2.1 Continuing the Installation After Solving the Problem

As SAPinst does not abort the installation in error situations, there are two situations in whichyou can continue the installation:

Situation 1:

You have not canceled the installation. That is, the error dialog box is still displayed andSAPinst is waiting for your input. Proceed as follows:

On the displayed error dialog box, choose Retry .

SAPinst now retries the installation step.

Situation 2:

You have canceled the installation. That is, the installation is aborted and needs to becontinued. Since SAPinst records the installation progress in the file keydb.xml , it cancontinue the installation from the failed step without repeating previous steps.

You have two alternatives:

• Continuing the installation

• Restarting from scratch. That is, starting the installation with the delivered defaultkeydb.xml file.

In some cases, you must uninstall already installed components, before repeating theinstallation from scratch. That applies for example for an SAP System installation. Seethe uninstalling description in the corresponding installation guide.

How to proceed on UNIX

Continuing the Installation

a. Check if a SAPinst GUI Java process is still running, and if so kill it: ps -ef | grep java

b. Make sure that all environment variables are set as described in thecorresponding installation documentation.

c. Start SAPinst from your <SAPinst_INSTDIR> with: ./sapinst

Restarting from scratch

You have the following alternatives

• Restart the installation from installation CD

Start SAPinst from CD again as described in the corresponding installationdocumentation.SAPinst deletes all files in your installation directory and asks you if you want tooverwrite any existing installation directory.

• Prepare the new installation manually (installation CD is not needed)

In your <SAPinst_INSTDIR> do the following:

a. Rename the file keydb.1.xml file (original file delivered by SAP) to keydb.xml .

b. Delete all keydb.<no>.xml - files, if there are any.

c. Start SAPinst from your <SAPinst_INSTDIR> with: ./sapinst




Februar/2002 9

How to proceed on Windows

Continuing the Installation

a. Check if a SAPinst GUI Java process is still running, and if so, kill it by lookingfor javaw.exe under Processes in your Task Manager.

b. Choose Start → Programs → <menu_entry> → SAPinst Server with GUI (or SAPinst GUI if you want to start the GUI only or SAPinst Server only if you wantto start SAPinst without GUI).

Restarting from scratch

a. Check if a SAPinst GUI Java process is still running, and if so, kill it by lookingfor javaw.exe under Processes in your Task Manager.

b. Choose Start -> Programs -> <menu_entry> -> Prepare New Installation

c. Current log and command files will now be copied to a backup directory that

indicate day and time of the backup:<SAPinst_Dir>\log<month>_<date><time>

d. Choose Start → Programs → <menu_entry> → SAPinst Server with GUI (or SAPinst GUI if you want to start the GUI only or SAPinst Server only if you wantto start SAPinst without GUI).




10 Februar/2002

2.2 Known Symptoms, Errors, andSolutions

This section describes known symptoms, errors, and solutions.

What Does Symptom or ERROR means?

Symptom Describes an error situation that does not result in a defined error message.These situations are sometimes difficult to discover.

For example, you have started the SAPinst GUI, but after waiting a while youthink that there must be a start-up error, although no obvious messageappears at the command prompt.

ERROR Defines the ERROR message that is displayed either at your commandprompt or in the sapinst.log file, if not indicated otherwise. This section givesknown error messages. Sometimes messages of a type other than ERRORare given, if necessary.

For more information on SAPinst log files, see Log File [on page 19].

This section is divided as follows, depending on when the error occurs:

• When Starting SAPinst [on page 11]

• When Performing the Installation [on page 13]

Each category is divided into Symptoms and Error Messages.

Unique Error Message Identifier ERROR messages have now a unique identifier consisting of three letters and a 5-digit

number, for example MDB-06055.

This means, you can now search for solutions in this guide by simply entering the identifier

using the Find-routine (Crtl + F) of Adobe Acrobat Reader.

Only known errors are described in the following section. Updates as well asnew errors, their causes and plausible solutions will be provided on aregularly basis in this guide.In addition, an error message that implies an obvious solution is not explicitly

mentioned. For example, messages like: MOS-01109 Needed space on

mountpoint /test is 350000 KB, but got only 344203 KB.

For some installations, SAPinst does not provide unique identifiers. That is,you must enter strings from the error message text, to find the accordingsolution. This applies for the following SAPinst installations:

• SAP BW 3.0A

• IPC 3.0




Februar/2002 11

2.2.1 When Starting SAPinst

Symptoms

Symptom: For no apparent reason, SAPinst GUI does not start automatically. That is, thereare no messages at your command prompt to analyze the situation.

Situation

• On UNIX: You have run the install command from a CD-ROM (installs by default SAPinst and

SAPinst GUI on the host) or you have restarted the installation of SAPinst and SAPinst GUI withthe sapinst command.

• On Windows: You have started the installation with Start -> Programs -> <menu_entry> ->SAPinst Server with GUI or SAPinst GUI.

Solution

1. Abort the installation with Crtl + C.2. Check if the SAPinst GUI java process is still running, and if so kill it:

• UNIX: ps -ef | grep java

• Windows: Look for javaw.exe under Processes in your Task Manager.

3. Start SAPinst from your installation directory again :

a. sapinst SAPINST_NO_GUISTART=true

b. Start SAPinst GUI

UNIX: startinstgui.sh / Windows: startinstgui.bat

ERROR Messages at your command prompt

Trace [iaoxcguist.cpp:110] dostart GUI( ): dostart GUI( ) returns...

Cause

SAPinst GUI start-up error due to local settings. Known reasons are:

• Pre-existing *.jar files from Non-SAP-XML parsers (for example xerces.jar) in your JRE

ext directory

• UNIX: You use an Xserver with incorrect permissions to perform the installation on another UNIXhost (Xhost)

Solutions

• For the ext directory problem

Check if there are already <xml_parser>.jar files in your ext directory. The default path is:

<JAVA_HOME>\JRE\lib\ext (on Windows) / <JAVA_HOME>/JRE/lib/ext (on UNIX)

If yes, rename those files, for example, to xerces.xxx.

• For the Xserver problem

On the Xserver enter the following command: xhost +<name>

where <name> is the host name of the Xhost.




12 Februar/2002

ERROR: fatal: sapcppstd.so open failed: no such file or directory

Cause

You have started SAPinst on operating system Solaris or Compaq True 64, but the library path

environment variable is not set correctly.

Solutions

1. Extend your LD_LIBRARY_PATH environment variable with ".":setenv LD_LIBRARY_PATH .

2. Run SAPinst again:

./sapinst

FGE-00006: Trying to establish a connection failed. Check whether the ports <port_number1>or <port_number2> are already in use.

Cause

SAPinst uses two ports (default 4999 and 5000) to connect to SAPinst GUI but the ports are alreadyin use.

Solutions

• Check if another instance of SAPinst or SAPinst GUI is already running. If yes, cancel theseinstances.

• Check if the SAPinst GUI java process is still running and kill it as follows:

- UNIX: ps -ef | grep java

- Windows: Look for javaw.exe under Processes in your Task Manager.• On UNIX: Start SAPinst in your <SAPinst_INSTDIR> using a free port number:

sapinst SAPINST_DIALOG_PORT=<port>

whereas <port> is an unused port on your host. For example, if you enter 6000 as <port>,

SAPinst uses the ports 6000 and 6001.

• On Windows:If you have run setup.cmd from the installation CD, you must do the following:

a. Copy directory SAPINST/NT from the installation CD to your local hard disk.

b. In file SAPINST/NT/Setup.cmd search for the following string:

.\sapinst.exe SAPINST_CONTROL_URL=control_bootstrap.xml

c. Append SAPINST_DIALOG_PORT=<port> to this string:.\sapinst.exe SAPINST_CONTROL_URL=control_bootstrap.xml SAPINST_DIALOG_PORT=<port>

whereas <port> is an unused port on your host.

d. Run Setup.cmd from your local hard disk.

If you have started SAPinst via the windows start menu, you must do the following:

a. Open a command prompt.

b. Change to your <SAPinst_INSTDIR> and run.\sapinst.exe SAPINST_DIALOG_PORT=<port>

whereas <port> is an unused port on your host.




Februar/2002 13

2.2.2 When Performing the Installation

Symptoms

Symptom: You have the impression that the installation procedure is hanging, but you are notsure about the situation.

Situation

During the input phase (in which you enter installation parameters) or processing phase (in which thesystem performs the actual installation), you have the impression that the system is not proceedingwith the installation procedure.

You want to check the situation.

Solution

Check the command window that is always present beside the SAPinst GUI to see if something has

happened:− If you see moving lines, the installation is running.

− UNIX: An error message might be displayed, but the error message dialog box is sometimeshidden behind the SAPinst GUI dialog. Therefore, minimize the SAPinst GUI dialog.

− If there are neither moving lines nor error messages displayed, switch to the SAPinst GUIand choose Next again if possible. You can move the mouse slightly to see if the mousepointer changes its shape, which indicates that the Next button has been pressed.

ERROR Messages

ERROR messages that are displayed in the log viewer, the relevant sapinst.log or other log files that are referenced in sapinst.log.

If you can solve the problem using this section, try to continue the installation [on page 7].

SAPinst specific

FSH-00006: Return value of function chownU (/usr/sap/trans/tmp, <number>,<number>) is<number>

Cause

You are installing a SAP System on UNIX with deactivated Network Information Service (YP). Thereis already one (or more) SAP System installed in your network environment.

A user-ID or group-ID that you just want to create during the installation does not match with the ID'sof the already existing users or groups (for example for group sapsys or dba).

Note: MOS-01085 and MOS-01105 are also displayed as subsequent messages in this context.

Solutions

If you are asked for group-ID or user-ID during the installation in such a situation (deactivated NISwith pre-existing SAP Systems), you must enter exactly the already existing IDs of the correspondinguser or group.




14 Februar/2002

MOS-01232: pNT_ACCOUNT_NAME must not be an empty string

Cause

You have started setup.cmd in order to run an installation in a Windows NT 4.0 domain where a

UNIX-Samba host is defined as Master Browser , which causes an account dissolving error.

Solutions

You have to use a Windows host as Master Browser . Try to disable your UNIX-Samba as Master Browser host as follows:

a) Find the UNIX-Samba Master Browser for your domain (for example by means of the command

browmon.exe from the Windows NT 4.0 Resource Kit).

b) On your UNIX-Samba host set the following browse options in the smb.conf file to no:

− local browser = no

− preferred browser = no

− domain browser = no

c) Restart both your Windows NT 4.0 host and your UNIX-Samba host.

d) Repeat the steps above for all UNIX-Samba hosts that are displayed as Master Browser when

starting the resource kit browser monitor (browmon.exe ).

FGE-00015: Could not create XML document (DOM) from file

Cause

The dialog.xml file could not be found in your installation directory.

Solutions

Copy the original dialog.xml file from the installation CD to your installation directory.

UNIX: Make sure that the file is written in lowercase only.

FGE-00013 / FGE-00014: There are parse errors in ...

Cause

An XML file could not be parsed because it has been changed incorrectly.

SolutionsInform SAP about the problem, as described in step 4 of Identifying Errors and Solving Problems[page 8].




Februar/2002 15

FCO-00020 : The control file <file_name> could not be parsed. The following problemsoccurred: <problem>

CauseThe control.xml file could not be parsed because it has been changed incorrectly.

Solutions

Inform SAP about the problem, as described in step 4 of Identifying Errors and Solving Problems [onpage 7]).

FCO-00022 : The control file <file_name> is inconsistent.

Cause

Fatal error

Solutions

Inform SAP about the problem, as described in step 4 of Identifying Errors and Solving Problems [onpage 7]).

FCO-00016 : The control file <file_name> is inaccessible.

Cause

The file control.xml could not be found in your installation directory.

Solutions

Copy the original control.xml file from the installation CD to your installation directory.

UNIX: Make sure that the file is written in lowercase only.




16 Februar/2002

SAP System specific

ERROR in SAP<TABART>.log : file /../<SID>/DB/SAPAPPL0.TSK.bck already seems to exist a previous run may not have been

finished cleanlyfile /../<SID>/DB/SAPAPPL0.TSK possibly corrupted

/sapmnt/<SID>/exe/R3load: job finished with 1 error(s)

/sapmnt/<SID>/exe/R3load: END OF LOG: 20011213092725

Cause

Error in the processing sequence of the R/3 load

Solutions

Read SAP Note 455195.

MDB-06055 : Range error: Field numberOriglogDirs must be in range [2,25]. Actual value is 0.

Cause

You have set the number of mirrored redo log files to 0 during a SAP System installation on

UNIX/Oracle but the value must be greater than 0.

Solutions

a) Copy the file keydb.xml from your installation directory <SAPinst_INSTDIR>

to sapserv (SAP Note 40024)

b) Create OSS error message

MOS-01011: DBR3LOADEXEC_IND_IND InternalInstallationDo:0 SyFilesWithPatternRead(NULL) returned with 0STR FILES FOUND: 0

Cause

You perform a SAP System installation on UNIX and the installation CDs has been probably copiedmanually to disk. This may cause the following (known) errors:

a. The installation CD has been copied incompletely to disk.

b. Solaris / AIX: During the copy procedure an unwanted automatic conversion of all file anddirectory names occurs, changing all capital letters to small ones.

Solutions1. Check the correctness of your copied files anyway (completeness / capital letters)

2. If you find lower case letters repeat the copy procedure as described in SAP Note 459899 intopic: SOLARIS/AIX: Copying CDs

3. Continue the installation by running ./sapinst in the <SAPinst_INSTDIR>.




Februar/2002 17

3 RestrictionsThe following summarizes known restrictions:

• You must not modify the SAPinst XML files, especially the file keydb.xml, unless SAPdelivers a description for the modification.

Only perform the installation by using SAPinst GUI as described in the installationdocumentation.




18 Februar/2002

4 Technical Information

4.1 Important Files in the InstallationDirectory

4.1.1 Overview After having started SAPinst from the installation CD-ROM, the following files are in the

installation directory <SAPinst_INSTDIR> :

Files Description

Operating System Independent

*.xml SAPinst command files

*.dtd Corresponding document type definitions for the XML files

*.log Default log files

JAR (SAPinst GUI host

only)

Directory: JAR Files for the Java-based SAPinst GUI

UNIX only

*.sl (HP-UX)

*.o (IBM)

*.so (other)

Shared libraries to run SAPinst

sapinst Command to start the component installation with SAPinst

startinstgui.sh

(SAPinst GUI host only)Script to start the SAPinst GUI manually

SAPCAR SAP's archive utility

Windows only

*.dll Dynamic link libraries (DLLs) to run SAPinst

sapinst.exe Command to start the component installation with SAPinst

startinstgui.bat

(SAPinst GUI host only)Batch file to start the SAPinst GUI manually

sapcar.exe SAP's archive utility

*.cmd Command files




Februar/2002 19

4.1.2 Important XML FilesThe SAPinst command files determine how SAPinst performs the installation of the SAPSystem.

All control flow, parameter, and other information is stored in XML documents. These are themost important documents and their contents:

XMLdocument

Contents

control.xml Instructions for controlling the installation of SAP components

keydb.xml Table containers for installation parameters.

When you run SAPinst for the first time, the delivered default keydb.xml

file is copied to keydb.1.xml.

If you run SAPinst several times in your installationdirectory, the system copies the keydb.xml to

keydb.<No>.xml .

However, keydb.1.xml always remains the original default

keydb.xml delivered by SAP.

messages.xml Mapping of message IDs to message texts

dialog.xml Description of the dialog form

packages.xml Required label pattern for CD ROM

The control.xml file assigns dialogs and installation steps to all components that might be

installed. That is, control.xml is used in every phase of the installation.

During the input phase of the installation, your input is written to the keydb.xml file, whichis then used during the processing phase of the installation. That is, keydb.xml contains all

installation parameters for the component to be installed.

4.1.3 Log FilesSAPinst records all information about the installation process by default in the log file

sapinst.log:

• UNIX: <SAPinst_INSTDIR>/sapinst.log /

• NT: <SAPinst_INSTDIR>\sapinst.log

Additional log files might be written during the installation process. These

additional logs are referenced in sapinst.log.

Additionally, there are other log files: sapinst_dev.log and instgui.log

(SAPinst GUI host only), but these files are not relevant to analyze error situations. They are for support purpose only.




20 Februar/2002

Message Content Overview

Message Type Meaning

Info

Warning

Error

Trace

These are the default settings that show installation progress.

Every time you start SAPinst in an installation directory, SAPinst generates

a new sapinst.log with the contents of the former sapinst.log (which

is saved to sapinst.<NR>.log ) and appends the new log information.

Trace and Error types are also displayed at your command prompt.

Flow Trace States more detailed information about the installation progress andsuccess.Might be useful during error situations. For detailed information, restartSAPinst as follows:

a. Set environment variable FLOW_TRACE to enabled.

b. Start SAPinst as follows:

sapinst SAPINST_MESSAGE_THRESHOLD=flow_trace

Message Sections Meaning

Phase Group of installation steps that process a meaningful unit, such as checkingfile systems.

Phases cannot overlap. That is, when a new Phase begins, the old one isautomatically finished.

Transaction Group of installation steps that is a more detailed unit of a Phase.

Beginning and end of a transaction is clearly marked.

A sapinst.log example:

PHASE 2001-11-09 15:43:35

Prepare check/adapt SAP instance filesystem

...

***** Transaction begin *****

TRACE

Need 350000 KB on mountpoint /, got 344203

ERROR 2001-11-09 15:43:53

Needed space on mountpoint / is 350000 KB, but got only

344203 KB

TRACE

Need 460000 KB on mountpoint /test, got 4.0859e+07 KB

INFO 2001-11-09 15:43:53Needed space in directory /oracle is 50000 KB.

ERROR

***** Transaction end with error *****

ERROR 2001-11-09 15:43:54

An error occurred during the installation.




Februar/2002 21

4.2 External Support Tools

In special cases, you might need to look at SAPinst's XML files, for example, to provide our hotline support with precise information about the state of the installation. To simplifyhandling of XML data we recommend using one of the following XML editors, both of whichare available in a trial version on the Internet:

• Xeena (from IBM Haifa Research Lab, Israel) in Java for Unix and Windows:

http://www.alphaWorks.ibm.com/tech/xeena

• XMLSpy (from Altova, Inc.) for Windows only:

http://www.xmlspy.com




22 Februar/2002

4.3 SAPinst Start-up Options

4.3.1 Command OverviewUse one of the following commands to start the installation with SAPinst:

• Starting from the installation CD ROM:

− UNIX: INSTALL

− Windows: setup.cmd

SAPinst is then copied to your installation directory.

• Starting from your local installation directory

− UNIX: ./sapinst or ./startinstgui.sh (SAPinst GUI only)

− Windows: Normally, you use the Start menu. However, you can also use the

command line:

sapinst or startinstgui.bat (SAPinst GUI only)

4.3.2 Command Options OverviewThe following summarizes the most important command options:

Command Options Description

--nogui Copies SAPinst without SAPinst

GUI to your installation directory

--nosapinst Copies SAPinst GUI only to your installation directory

--port <port> SAPinst uses the ports 4999 and5000 during the installation for communication with SAPinst GUI.If one of these ports is alreadyused by another service you mustrun INSTALL with the --port

option, where <port> defines an

unused port number.

For example, if you enter 6000 as<port>, SAPinst uses the ports

6000 and 6001.

INSTALL

--instdir

<SAPinst_INSTDIR> Automatically creates the given<SAPinst_INSTDIR > with

required permissions (777).

Then copies SAPinst from CD tothe <SAPinst_INSTDIR >.




Command Options Description

SAPINST_DIALOG_PORT=<port> Starts SAPinst using the specified

<port> (in principle the same asdescribed above for the INSTALL

command).

./sapinst

sapinst

SAPINST_NO_GUISTART=false Starts SAPinst without SAPinstGUI.Only relevant for UNIX. OnWindows platforms you canchoose this option using the Start

menu.

-port <port> Starts SAPinst GUI using thespecified <port> (in principle the

same as described above for theINSTALL command).

startinstgui.sh

startinstgui.bat

-host <hostname> Connects SAPinst GUI to the<hostname> specified.

Only relevant for remoteinstallations. For more informationon remote installation, see your component installationdocumentation.

sapinst troubleshooting guide

Documents