1827280 Members
2375 Online
109717 Solutions
New Discussion

Re: SAM error

 
SOLVED
Go to solution
Lance Leung
Advisor

SAM error

My HP machine ran out space while installing a patch depot (the initial Install Analysis said it was okay). It was stuck somewhere and after a reboot, I have been getting internal error whenever I access some areas in SAM. In addition, there is no boot.config file. And when I tried to generate it again with getkinfo -b, I got another SAM error as follows:

"Attempting to read default values for kernel configuration (drivers, subsystems, devices, and tunable parameters) from both the *.tx files in /usr/sam/lib/kc and from /usr/conf/master.d/*.@!@16@1007132144@0
Syntax Error: /usr/sam/lib/kc/kc.da at line 2: Location: da_parse:734 Error Code: 7159"

Does anyone know what means or the steps to fix the problem? Thanks.

Lance
4 REPLIES 4
S.K. Chan
Honored Contributor
Solution

Re: SAM error

The above errors usually indicate that some installation was not properly configured. Verify that the SAM filesets are configured. Do this :-
1. Check the state of all SAM filesets, make sure they are all configured:
# swlist -l fileset -a state | grep -i sam
2. Issue the following command to check for anything that isn't configured:
# swconfig \*
3. Once again, verify that all installed filesets are configured:
# swlist -l file -a state | grep -i sam
4. If a patch is either installed, transient, or corrupt after completing Steps 1 through 3, then re-install the SAM patch with the following options:
# swinstall -x autoreboot=true -x match_target=true -x reinstall=true -x reinstall_files=true -s /tmp/.depot
5. Use the cksum command to verify that /usr/sam/lib//.yy has the same size, as per the patch text that was installed on the system.
Eg:
1394563708 6711 /usr/sam/lib/kc/kc.da

This process should resolve the problem. If the problem persists, and all patches are in configured state, it is possible that the

/usr/newconfig/etc/sam/reg_*

files were not copied to /etc/sam.

These files synchronize SAM's registration files to the executables under /usr/sam. Complete the following steps if the problem persists:

1. Check that the /usr/newconfig/etc/sam/reg_* files have been copied to /etc/sam:
# ls -l /usr/newconfig/etc/sam/reg_* /etc/sam/reg_*

2. Compare the file sizes.
Note: If there are differences, execute these :

# cp /usr/newconfig/etc/sam/reg_* /etc/sam

If SAM continues to fail, check the install logs for clues as to what may have happened during the install phase:

/var/adm/sw/swagent.log and
/var/adm/sw/swinstall.log

Anthony deRito
Respected Contributor
Michael Tully
Honored Contributor

Re: SAM error

Hi,

Three further things:

After the swconfig has ran, make sure you can
compile a kernel.

Second thing is to make sure that you sufficient disk space available to do patches, i.e. run the 'cleanup' command before starting any patch installation.

Make sure you have an up to date make_recovery
tape cut prior to any patch installation.

-Michael
Anyone for a Mutiny ?
Lance Leung
Advisor

Re: SAM error

Thanks for all the hints. I haven't gone through the steps yet but I am sure this will work. Thanks.

Lance