Activant Solutions Inc.

The System Administrator’s Guide to Surviving the Morning

Objectives

Troubleshoot common errorsIdentify copy errors and the proper procedure to remedy themStart and stop Progress database serversExpand the AIX file systems

This course will NOT cover…

Basic AIXAIX backupsAIX errorsCreating the End of Day JCMEditing the End of Day JCM

Copy Errors

Occur during two phases of operationWriting to tapeVerifying tape

Three major divisions of errorsMediumHardwareNot Ready

Tape Drives and Errors

Copy Tapes

High quality tapes should be usedIBM, Sony, Imation

Match tapes and tape driveTapes DDS2Tape Drive DDS2

One tape for each day of the weekLife cycle about 6-9 months

Tape Drive Cleaning

Should be done once a weekMore often if environment is dirty

Cleaning cartridgeis good for 50 uses

Do NOT rewind!Discard when all tape is on the right side

** IBM cleaning cartridge is recommended **

This is Decision Time!

STOP or GO

RSK Medium

SRSSRS--Track Following Error 0x09Track Following Error 0x09Cause

Tape drive is dirtyBad tape

ResolutionClean tape drive headsTry the copy againReplace the tape

Continue: NORetry: YES

RSK Medium

SRSSRS--Media Not LoadedMedia Not Loaded--0x090x09

CauseTape is bad

ResolutionRun cleaning tapeTry the copy with another tape

Continue: NORetry: NO

RSK Medium

SRSSRS-- UnrecoveredUnrecovered Read ErrorRead Error--0x110x11Cause

Tape drive is dirtyTape is bad

ResolutionRun cleaning tapeTry copy againTry copy with new tape

Continue: NORetry: YES

SRS Track

FollowingError 0X09

SRS Media Not

LoadedError 0X09

SRSUnrecovered

ReadError 0X09

Tape drive is dirty.

Run the cleaning tape.

Replace the tape.

Try the copy again.Tape

is bad.

SolutionERROR

CAUSE

RSK Medium

SRSSRS--Data ErrorData Error--0x110x11Cause

Tape drive is dirtyTape is bad

ResolutionRun cleaning tapeTry copy againTry copy with new tape

Continue: NORetry: NO

RSK Medium

CauseDirty tape or driveTape is bad

ResolutionRun cleaning tapeTry to copy with another tape

Continue: NORetry: YES

SRSSRS--No Record FoundNo Record Found--0x140x14

RSK Medium

SRSSRS--CmdCmd ToTo--0x310x31Cause

Tape not seated properly or bad tapeTape drive needs to be reset

ResolutionRun cleaning tapeTry copy with another tapeRun system shutdown

Continue: NORetry: YES

RSK Hardware

Have you seen a RSK Hardware error?

RSK Hardware

SRSSRS--Write ErrorWrite Error--0x030x03

CauseUsually happens after tape drive replacementOriginal drive was writing bad tapes

ResolutionDiscard all tapes from the old tape drive

RSK Hardware

SRSSRS--Target Internal ErrorTarget Internal Error--0x440x44Cause

Tape not seated properlyBad tape

ResolutionRun cleaning tape and try copy againTry a different tapeRun shutdown on the system

RSK Hardware

SRSSRS--Cartridge FaultCartridge Fault--0x520x52

CauseTape may not have loaded properlyTape may be bad

ResolutionReload tape and try againTry new tape

SRS Write Error

-0X03

SRS Target

InternalError 0X44

SRS Cartridge

Fault -0X52

Tape drive replacement

Tape not loaded property

Bad tapeOriginal drive was writing bad tapes.

ERROR

CAUSE

SRS-Cartridge

Fault-0X52

SRS-Target

InternalError-0X44

SRS-WriteError-0X03

Discardtapes fromold drive.

Runcleaningtape.

Use a newor differenttape.

Runshutdownon system.

Reloadandtry again.

SolutionERROR

RSK Not Ready

SRS-Drive Not Ready-0x04

CauseTape may not be in the tape driveTape drive lost communication with system

ResolutionLoad tape in tape driveRun shutdown on system

RSK Not Ready

CauseTape not in driveBad tape

ResolutionLoad tape in driveTry copy againReplace the tape

SRS-Medium Not Present-0x3A

ERROR

CAUSETape is bad.

Tape may not be in the drive.

Tape drive lost communicationwith the system.

SRS-Drive

NotReady-0X04

SRS-Medium

NotPresent-0X03A

SolutionERROR

Load a tape.

Replace the tape.

Try copyagain.

Run shutdownon system.

SRS-Drive

NotReady-0X04

SRS-Medium

NotPresent-0X03A

Progress Errors

Progress database servers have two modes of operation

Single UserMulti-User

Often occur after daily end of day JCM does not complete successfully

Generated because progress servers did not automatically restart

Progress Errors

Progress Database Servers

Single user modeAllows progress database to be availableOften used to perform system database maintenanceOnly command console can access the progress database

Progress Database Servers

Multi-User modeAllows all users access to progress databasesThis is the standard mode of operation

Progress Database Servers

Stopping Progress serversMust be logged in as the root userShould have the P21 system stopped

UTILITY COMMAND- ST

If system does not respond with “stopped”locate the users that are still activelog them out

Run the “**STOP” to force user off

Progress Database Servers

Stop Progress database servers for all systems#/usr/lpp/p21pro/bin/p21shut

Can change directories to execute#cd /usr/lpp/p21pro/bin#./p21shut

Procedure will display, as it executesReturn to “#” prompt when complete

PROSTARTUP

Starting Progress Database Servers

Must be logged in as root#/usr/lpp/p21pro/bin/p21serve

Can change directories to execute#cd /usr/lpp/p21pro/bin#./p21serve

Displays each server as it restartsMay take several minutes to execute

AIX File Errors

AIX File systems are static in natureViewed with the “df” commandExpanded while system is up and runningMust be logged in as AIX root user to expand

df listing

df listing with File System

/usr/lpp/p21pro/db highlighted

Full File Message

Error message/usr/lpp/p21pro/db is 90% used

File system /usr/lpp/p21pro/dbUsed for storage of P21 data for Payables, Receivables, General Ledger

MUST BE MAINTAINED to preserve the integrity of P21 data

Expanding File System

Check Disk Drives on system#lspv - output similar to following

hdisk0 00825102924a2ff6 rootvghdisk1 00002145b2496f5c rootvghdisk2 005476hd89421h7b p21vg

Also displays volume group assigned to each drive

Expanding File System

Done directly from command linePerformed through SMIT menus

System Management Interface Tools

Certain file systems can be over 90%ok to remain that way

Expanding File System

On which Volume Group the file system reside?#lslv p21prodblv

Displays info associated with logical volumevolume groupPP sizetotal LP’s used

lslv listing

Expanding File System

Is there is sufficient disk space available on the volume group?

#lsvg rootvg

Crucial info for the volume group displays

lsvg command

Expanding File System

Is there an ability to add space?To what volume group does the file system belongs?Does the volume group contain available disk space?

Expand only if required!Apply only minimum disk space required!

Expanding File System

CAN be expanded “on the fly”CAN be expanded “on the fly”CANNOT not be reduced “on the fly” CANNOT not be reduced “on the fly”

Requires AIX back up and considerable Requires AIX back up and considerable “downtime”“downtime”

!Use extreme care when expanding file system!Use extreme care when Use extreme care when expanding file system!expanding file system!

Expanding File System

Done directly from command linePerformed through smit menus

System Management Interface Tools

Certain file systems can be over 90%Ok to remain that way

Expanding File System from the Command Line

Must be logged in as rootEx: # chfs -a size=+1 /dev/p21prodblvAdd one partition to the file system

Run several times until file system is below 80 %

Expanding File System… using SMIT menu

Must be logged in as root userEx: smit chfs

smit chfs

smit chfs

smit chfs

Summary

Identify and troubleshoot common errorsRSK MediumRSK HardwareRSK Not Ready

Start and Stop progress database serversExpand AIX file system

For More Information…

Acclaim Help FilesVisit Activant on the web:http://distribution.activant.com/

View Educational Services course offeringsAIX 101 CBT: AIX Administration - The Basics

Browse DocumentationSystem Administration Manual

Search the Solutions databaseSubmit a Support case

E-mail Professional Services Salespss@activant.com