Console Issues

• Editing Host Properties in a Zone Might Cause Database Problems (CR 6545220)

• Large Reports Might Cause the Console to Crash

• uce_console command is not in the /usr/bin Directory on Solaris

• Opening the Job Log in the Console Can Take Several Minutes on a Zoned System (CR 6508689)

Editing Host Properties in a Zone Might Cause Database Problems (CR 6545220)

Description:

In Sun Connection 1.1.x, if a system contains zones and you attach a profile to the host properties in a local zone, the system is no longer displayed in the console.

---

Caution –

Do not edit host properties in the global zone. If you do, the database will become corrupted and will require manual intervention.

---

Large Reports Might Cause the Console to Crash

Description:

In Sun Connection 1.0.x, running large reports might crash the console.

uce_console command is not in the /usr/bin Directory on Solaris

Description:

When the console package is installed on Solaris, the convenience link for uce_console is made in the console package's bin directory rather than /usr/bin as it is on Linux.

Workaround:

Add /opt/SUNWuce/console/bin to the user's PATH shell variable. uce_console will then be available without entering the full path name.

Opening the Job Log in the Console Can Take Several Minutes on a Zoned System (CR 6508689)

Description:

When a job is run on multiple agents installed in zones on a system, attempting to open the job log in the console for any one of the jobs can take as long as 10 minutes.

Workaround:

Seekers are still running on the agent which causes the agent to be slow to respond. Once the seekers have finished running, the job log will open in 1-2 seconds. Wait for agents to complete running the seekers.