test

Sun N1 Service Provisioning System 5.2.1 Release Notes

Runtime Issues

This section describes known runtime issues.

Windows: Database Optimization Should Be Performed On a Regular Basis

If database optimization is not performed on a regular basis, performance deteriorates.

Workaround: Manually schedule a database optimization task.

This is a two phase process.

Note –

The following steps are performed on the Master Server.

  1. Creation of Database Optimization Script

    Create a new Windows command file called file_name.cmd in the server\bin\ directory of the Master Server installation. Copy the following text to the file_name.cmd file.


    REM No changes need to be made to the script after this line
cd %SPS_MS_DIR%\bin
..\cygwin\bin\bash.exe roxdbcmd vacuumdb -d rox

  2. Scheduling

    1. Choose Start ⇒ Settings ⇒ Control Panel ⇒ Scheduled Tasks.

    2. Start the Task Scheduler Wizard by double-clicking Add Scheduled Task in the Scheduled Tasks folder. Click Next.

    3. Click Browse to open the Select Program To Schedule dialog box. Navigate to the optimizedb.cmd file.

    4. Choose the frequency of task runs.

      It is recommended that you run the task daily. Your options in subsequent screens will depend on your choices. The following steps assume that the user selected the daily option.

    5. Enter the time when the task should be run. Click Next.

      Note –

      It is advisable to run the database optimization task when the system is not being used. Choose the scheduling time accordingly.

    6. Type the name and password of the user who is associated with this task. Click Next.

      Make sure that you choose a user with sufficient permissions to run the program. By default, the wizard selects the name of the user who is currently logged on.

    7. Click Finish.

      The task is scheduled.

    8. For confirmation of successful task scheduling, it is advisable to choose Start ⇒ Settings ⇒ Control Panel ⇒ Scheduled Tasks and check the Task Exit Status Code. A successful task run is indicated by code 0x0.

      Note –

      Please note that the scheduled run of the task should be completed before observing the exit status code.

      For more information on Windows task scheduling options, see http://www.microsoft.com/technet/scriptcenter/guide/sas_man_lpja.mspx.

Backup and Restore Commands Fail To Restart Master Server (6398090)

When the backup and restore scripts are run, the Master Server with an SSL configuration fails to restart after the execution of these commands.

Workaround: Perform one of the following options:

Folder Add Command Fails With Permission Problems (6382198)

When a user tries to create a folder by using the fdb.f.add command, folder creation fails despite the parents argument being set to true.

Setting -parents true, only creates the new folder and its immediate parent. The following example fails because folder f1 does not exist.


r_cli -cmd fdb.f.add  -parents true -fullname /group1/f1/f2/f3 -u user1 -p user1

The following error message is displayed:

Unable to save folder /group1/f1/f2/ due to permissions problem. (013011) access denied (com.raplix.rolloutexpress.systemmodel.userdb.FolderPermission folder:129159219047-1139319070874-31478-1381549121 write)

This happens when a user does not have administrator rights, but is a member of the group that owns the folder.

Workaround: When using the -parents true option, do not require the command to create more than the new folder and its immediate parent.

Container Component Creation Fails When Platform Is Not Equal To system#any (6408383)

If you attempt to create a component of type system#container and platform is not equal to system#any, component creation fails. The following error message is displayed:

Unable to perform the requested operation An unexpected error occurred. Try using the menu on the left or other links on the page to navigate to the page you want and try again.

Workaround: Perform one of the following:

Snapshot Data For Nested Components Might Not Be Purged When the Nested Components Get Reinstalled

If a nested component that is installed by way of the installation of a container component, creates snapshots, the snapshot data on the Remote Agent might not get purged when the nested component is uninstalled by the reinstall of the container component. This might lead to the Remote Agent, on which the nested component was installed, to consume more disk space than it should since the orphaned snapshot data was not purged.

Workaround: The orphaned snapshot data might be purged by installing and then uninstalling a simple component that creates snapshots on the Remote Agent with orphaned snapshot data. The install and uninstall cause the Remote Agent to compare its snapshot data with the Master Server. The result is that the snapshot data is purged for all the components that are no longer installed on the Remote Agent.

System Might Hang When Using SSL on Red Hat Linux Advanced Server 3

If you are running the Sun N1 Service Provisioning System on Red Hat Linux Advanced Server 3, the system might hang when using Secure Socket Layer (SSL) connections.

SSL uses SecureRandom which uses /dev/random to generate random numbers. Red Hat Linux Advanced Server 3 includes a bug that causes /dev/random not to collect entropy. Since /dev/random does not generate numbers unless sufficient entropy is collected, applications hang when attempting to read random data from /dev/random.

Workaround: Choose one of the following workarounds:

Plan Execution Pauses for 10 Minutes on execJava in Preflight on IBM AIX Remote Agents (6313197)

On an IBM AIX remote agent, the plan execution for CreateManagedServerPlan might pause for 10 minutes on an execJava step.

Workaround: None.

Check In Current Does Not Report Errors for Components That Do Not Support Check In Current (5063014)

The Check In Current operation enables you to ensure that the version of a component in the Master Server repository is the most recent. The Master Server checks its version of the component against the version on the source host. The check is based on metadata regarding the location of the component that was gathered at the time of previous check in.

You cannot perform the Check In Current operation on all component types. Typically, component types that can be browsed using the browser interface are eligible for the Check In Current operation.

When performing a bulk Check In Current operation, if you select a component type that does not support the Check In Current operation, the operation completes with no errors. The results displayed in the Progress dialog box for component types that are not supported might be empty or might represent historical data.

Workaround: No workaround is available.

System Might Hang When Using SSL on Red Hat Linux Advanced Server 3.0 (5084676)

If you are running the Sun N1 Service Provisioning System on Red Hat Linux Advanced Server 3.0, the system might hang when using Secure Socket Layer (SSL) connections.

SSL uses SecureRandom which uses /dev/random to generate random numbers. Red Hat Linux Advanced Server 3.0 includes a bug that causes /dev/random not to collect entropy. Since /dev/random does not generate numbers unless sufficient entropy is collected, applications hang when attempting to read random data from /dev/random.

Workaround: Choose one of the following workarounds:

Notification Rules Might Cause Plans to Run Slowly (6176243)

If you create a notification rule that has few criteria or no criteria, plans might appear to run slowly. The plan does not complete slowly, but the display of the plan results might be delayed.

Workaround: When creating a notification rule, use as many criteria as possible. More criteria for a notification rule decreases the number of notification emails the provisioning system sends across the network. A lower number of notification emails is less likely to interfere with the display of plan results.