Sun Microsystems Portal Server 6 2005Q1, Planning Manual

Page: 160 / 192

Troubleshooting Portal Server
160 Portal Server 6 2005Q1 • Deployment Planning Guide
./uxwdog -d
portal-server-install-root
/SUNWam/servers/https-
server
/config
ns-httpd -d
portal-server-install-root
/SUNWam/servers/https-
server
/config
Admin Web Server (optional, but usually running):
./uxwdog -d
web-container-install-root
/SUNWam/servers/https-admserv/config
ns-httpd -d
web-container-install-root
/SUNWam/servers/https-admserv/config
Log Files
Examine the following log files for errors.
Sun Java System Web Server (
errors
and
access
):
web-container-install-root
/SUNWam/servers/https-
server
/logs
Sun Java System Directory Server:
/var/opt/SUNWam/logs
Recovering the Search Database
The Search database maintains recoverable transaction logs. Thus, under normal
circumstances, you do not have to do anything to recover the database. Recovery
from errors and transient conditions such as a full disk are straight forward. If
desired, maintain Search database archives and restore from an archive in case you
lost the entire database. In this scenario, you would copy the archive to the original
database to recover it.
➤
To Recover the Database
1.
Stop all processes accessing the database, including the Portal Server instance.
2.
Use the
rdmgr -R
command to recover.
Working with the Display Profile
If you need to troubleshoot the XML contents of your portal’s display profile,
extract the contents to a file for examination. At some point in the troubleshooting
process, it might be useful to reload the display profile.