Sponsored Content
Operating Systems Solaris Problem with SMC after applying Patchset 1-148888-03 Post 302876840 by garydeena on Tuesday 26th of November 2013 10:29:30 PM
Old 11-26-2013
SMC broken

Hi All, Had same problem. Traced mine to a Java patch as well.
I had 125136-46 . Mine broke when I applied 125136-60.

As soon as I backed out, all was good.
 

7 More Discussions You Might Find Interesting

1. Solaris

SMC Help Please

We changed our root password on one of our Master NIS machines. We tried going into the SMC after the password change and it keeps failing for root login. I can login to the server via the root account. Just cannot open the SMC with the root account. This user is required to manage the users. ... (2 Replies)
Discussion started by: buckhtr77
2 Replies

2. Solaris

Smc

When I start SMC IT still doesnot work .It still remain configuration and don't change to welcome screen Please help me :mad: (1 Reply)
Discussion started by: iwbasts
1 Replies

3. Solaris

Jass & SMC login problem

After I run Jass , I can bring up the SMC GUI, but it wont let me log in as root. It works without Jass being run. Does anyone know what in Jass disables this. I have tried removing some things from jass like remote-root-login to no avail. Any hints would be greatly appreciated. I ram running... (0 Replies)
Discussion started by: garydeena
0 Replies

4. UNIX for Dummies Questions & Answers

smc problem

Hello, I've a Solaris 10. When I attemp to run SMC and click somthing there (for example "system information") , an error message is shown on the screen and says me WBEM is not running. (But actually WBEM is working). It says "if WBEM runing, I should stop/start wbem and try again." but I do it... (0 Replies)
Discussion started by: XNOR
0 Replies

5. Solaris

A little help with SMC

I installed the smc and now I'm getting the below error when i try to access it via web. Apache Tomcat/4.0.5 - HTTP Status 404 - /smconsole.jnlp The service Apache2 is in maintenance mode and I can't get it online. Can someone help with this please? Thanks. (5 Replies)
Discussion started by: bbbngowc
5 Replies

6. Solaris

Recommended patchset for Solaris and the patch bundle

Hello I recently downloaded and installed the latest patchset for Solaris 10 (update 5) running on SPARC. Actually I am new to Solaris (I come from Red Hat) and the security department asked me to update the system for security fixes. I logged in to Oracle support and used the recommended patch... (3 Replies)
Discussion started by: abohmeed
3 Replies

7. Solaris

New Patchset

Does anyone know what is going on with Solaris 10 and oracle? I am unable to download any new patchset, says I do not have permissions any longer . I am unable to get a response from them. Reason I ask, is that we had no warning, and company has a contract? (3 Replies)
Discussion started by: goya
3 Replies
SHAPE_PATCH(1)						      General Commands Manual						    SHAPE_PATCH(1)

NAME
shape_patch - shapeTools RMS generate patch file SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>] DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape patch from the top node of the central source repository creates a patch file for the whole system. The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH- FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output. Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure will leave an equally named patch file for each visited subsystem. The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1). INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit. SEE ALSO
shape_releas(1), vdiff(1), patch(1) FILES
<name1>+2+<name2>.pat 26.9.119 SHAPE_PATCH(1)
All times are GMT -4. The time now is 01:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy