Idsconfig/Solaris 9:update schema error

I'm currently trying get setup iDS 5.1 on Solaris 9 so that i can authenticate Solaris 8/9 against it. When i run idsconfig i get ERROR: update of schema failed! The logs show nothing useful, can anyone help please?
Thanks, Ian

I am having the same problem. ALL idsconfigs fail. I tried the CUSTOM installation, TYPICAL, and EXPRESS. All with the same results of idsconfig failing. Nothing in the log files either.

Similar Messages

Solaris 100 update manager

After initial installation of solaris 10 and updated system via update manager. I encountered a video card problema nd had to re-install solaris 10, now I am getting an error when I attempt to update solaris 10 update manager
Error: Patch metadata errors were deleted. Obselesce processing failure. Could not find obselescing update for 127717-01.
Where have I gone wrong.
Any assistance will be appreciated.

I re-installad solaris 10 and during the update I ommitted SMC updates. However, I noticed unique problem after re-installation. I tried to download anotther tool from sun site. It failed due to lack of disk space. I preallocated 32GB drive-space during installation, I later observed that I only had 1.4GIG of disk space remaining. It seems like I should not have preallocated the entire 32gig to solaris 10 during installation, or should I have taken a different approach. A little puzzled right now.
Thanks a bunch!!

Error in updating schema in SSM 7.0

Hi,
When I am updating schema in SSM 7.0, I am getting below error:
An Error has occurred in the scipt on this page.
Line:     67
Char:     3
Error:     'out1.1' is null or not an object
Code:     0
URL:     http://<server:50000>/strategy/bi/admin_bic_settcons.htm
Here I am loading cube from BW system.
Thanks
Anuj

Hi Anuj,
You mention in your first post you are loading cube. Are you really mapping a BW infocube to a PAS model? It is usually a good idea to build a query on top of the cube, makes it easier to control what is being imported to PAS.
Anyway, besides that message, can you find any error in the trace file? Search in the home folder for the trace file BICTRACE_SCHEMA_xxxxPBI.
Regards!
Ricardo Vieira

How to update schema-base xmltype by dba?error ORA-19007

Hi ,
Connect to db using user 'u1', register schema to LOCAL and update schema-base xmltype success. Then I login in db as dba, update xmltype occus ORA-19007. If I register the schema to GLOBAL, using dba to update xmltype has no problem. But how to update schema-base xmltype who's schema is register as LOCAL by dba?
connect to db using user ‘U1’：
declare
begin
dbms_xmlschema.registerSchema(
'http://www.oradev.com/myschetest.xsd',
'<schema xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.oradev.com/myschetest.xsd"
xmlns:sch="http://www.oradev.com/myschetest.xsd"
version="1.0" elementFormDefault="qualified">
<element name = "Employee">
<complexType>
<sequence>
<element name = "EmployeeId" type = "positiveInteger"/>
<element name = "FirstName" type = "string"/>
<element name = "LastName" type = "string"/>
<element name = "Salary" type = "positiveInteger"/>
</sequence>
</complexType>
</element>
</schema>',TRUE, TRUE, FALSE, FALSE);
end;
SCHEMA register as LOCAL.
create table globtest(id number, content sys.xmltype)XMLTYPE content STORE AS OBJECT RELATIONAL XMLSCHEMA "http://www.oradev.com/myschetest.xsd" ELEMENT "Employee";
It's OK.
insert into globtest values(1, sys.XMLType.createXML('<Employee xmlns="http://www.oradev.com/myschetest.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.oradev.com/myschetest.xsd http://www.oradev.com/myschetest.xsd"><EmployeeId>1234</EmployeeId><FirstName>Ravi</FirstName><LastName>Murthy</LastName><Salary>100</Salary></Employee>'));
It's OK.
update U1.globtest set content = sys.XMLType.createXML('<Employee xmlns="http://www.oradev.com/myschetest.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.oradev.com/myschetest.xsd http://www.oradev.com/myschetest.xsd"><EmployeeId>1234</EmployeeId><FirstName>'||unistr('\0080\0081')||unistr('\0085')||'Ravi</FirstName><LastName>Murthy</LastName><Salary>100</Salary></Employee>') where id=1;
It's OK.
but when i login in as dba,
using above update sql. It has probleam.ORA-19007.
How can i using dba to update this LOCAL schema-base xmltype? Thanks a lot.

User 'U1' is created by:
create user u1 identified by u1;
grant dba to u1;
Is there any other privilege need to be grant to u1?

Solaris 10 update 6 keeps generating core file (/core)

I wonder if somebody has encountered the following issue.
I did a fresh install of Solaris 10 update 6 on two servers (T5140 and T524) from DVD.
I noticed that a core file was in the root filesystem (/core).
So, I deleted it.
As soon as I delete the core file, another one is generated.
This is happening on both servers where I installed Solaris 10 update 6 from the DVD.
This is not a live update install. Solaris was installed from scratch. When prompted to preserve previous data, I replied with 'do not preserve data'
Does anybody know where the core file is coming from and how to stop it being generated?
Found out that is coming from vold
SunOS b1osdtsun02 5.10 Generic_137137-09 sun4v sparc SUNW,T5240
# more /etc/release
                      Solaris 10 10/08 s10s_u6wos_07b SPARC
           Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
                        Use is subject to license terms.
                            Assembled 27 October 2008
# mdb /core
Loading modules: [ libsysevent.so.1 libnvpair.so.1 libc.so.1 ld.so.1 ]
::statusdebugging core file of vold (32-bit) from b1osdtsun02
file: /usr/sbin/vold
initial argv: /usr/sbin/vold -f /etc/vold.conf
threading model: multi-threaded
status: process terminated by SIGSEGV (Segmentation Fault)
::stacklibc.so.1`strlen+0x18(408450a5, 0, 0, 88b70, 600, 180)
read_slices+0x114(874a0, b, 889a0, feeafd34, 1, 5)
read_hsfs_partition+0x88(b, 46c00, 6d0000, 2c, 34400, 1010101)
read_partition+0x30(874a0, 341a4, 3, 34000, 34400, 9)
create_top_partition+0x140(7cbe0, 7cc24, 7cbe0, 874a0, ffffffff, b)
0x265e0(800012, feeaff9c, c, 598e0, 7cbe0, ffffffff)
create_medium+0x74(800012, feeaff9c, 20, 12, 47800, c)
0x2232c(5d278, 0, 0, 800012, 20, 33000)
libc.so.1`_lwp_start(0, 0, 0, 0, 0, 0)
>
#It seems that vold is failing to mount the DVD on both servers after Solaris was installed.
Is this a Solaris 10 update 6 bug?
Edited by: shen on Jan 29, 2009 8:45 PM

Never mind.
It is a known bug documented on manual " [Solaris 10 10/08 Release Notes, Chapter 2 Solaris Runtime Issues|http://docs.sun.com/app/docs/doc/820-5245/chapter2-1000?a=view] " as shown below.
The solution is to apply vold patch [138130-01|http://sunsolve.sun.com/search/document.do?assetkey=1-21-138130-01-1].
Solaris 10 10/08 DVD Media Might Not be Automatically Mounted by vold (6712352)
The Solaris 10 10/08 DVD does not mount by default during runtime. No error message is displayed.
Workaround: Perform the following steps:
   1. Become superuser.
   2. Disable vold:
      * On Solaris 10 Systems:
            # svcadm disable -t volfs
      * On Solaris 8 and Solaris 9 systems:
            /etc/init.d/volmgt stop
   3. Mount the media manually by using the # mount -F hsfs path to block device path to mount point command. For example:
      # mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt

Solaris 10 update 9 - live upgrade issues with ZFS

Hi
After doing a live upgrade from Solaris 10 update 8 to Solaris 10 update 9 the alternate boot environment I created is no longer bootable.
I have completed all the pre-upgrade steps like:
- Installing the latest version of live upgrade from the update 9 ISO.
- Create and test the new boot environment.
- Create a sysidcfg file used by the live upgrade that has auto_reg=disable in it.
There is also no errors while creating the boot environment or even when activating it.
Here is the error I get:
SunOS Release 5.10 Version Generic_14489-06 64-bit
Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.
NOTICE: zfs_parse_bootfs: error 22
Cannot mount root on altroot/37 fstype zfs
*panic[cpu0]/thread=fffffffffbc28040: vfs mountroot: cannot mount root*
ffffffffffbc4a8d0 genunix:main+107 ()
Skipping system dump - no dump device configured
Does anyone know how I can fix this?
Edited by: user12099270 on 02-Feb-2011 04:49

Found the culprit... *142910-17*... breaks it
System has findroot enabled GRUB
Updating GRUB menu default setting
GRUB menu default setting is unaffected
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <s10x_u8wos_08a> as <mount-point>//boot/grub/menu.lst.prev.
File </etc/lu/GRUB_backup_menu> propagation successful
Successfully deleted entry from GRUB menu
Validating the contents of the media </admin/x86/Patches/10_x86_Recommended/patches>.
The media contains 204 software patches that can be added.
Mounting the BE <s10x_u8wos_08a_Jan2011>.
Adding patches to the BE <s10x_u8wos_08a_Jan2011>.
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system
Package SUNWio-tools from directory SUNWio-tools in patch 142910-17 is not installed on the system. Changes for package SUNWio-tools will not be applied to the system.
Package SUNWzoneu from directory SUNWzoneu in patch 142910-17 is not installed on the system. Changes for package SUNWzoneu will not be applied to the system.
Package SUNWpsm-ipp from directory SUNWpsm-ipp in patch 142910-17 is not installed on the system. Changes for package SUNWpsm-ipp will not be applied to the system.
Package SUNWsshdu from directory SUNWsshdu in patch 142910-17 is not installed on the system. Changes for package SUNWsshdu will not be applied to the system.
Package SUNWsacom from directory SUNWsacom in patch 142910-17 is not installed on the system. Changes for package SUNWsacom will not be applied to the system.
Package SUNWmdbr from directory SUNWmdbr in patch 142910-17 is not installed on the system. Changes for package SUNWmdbr will not be applied to the system.
Package SUNWopenssl-commands from directory SUNWopenssl-commands in patch 142910-17 is not installed on the system. Changes for package SUNWopenssl-commands will not be applied to the system.
Package SUNWsshdr from directory SUNWsshdr in patch 142910-17 is not installed on the system. Changes for package SUNWsshdr will not be applied to the system.
Package SUNWsshcu from directory SUNWsshcu in patch 142910-17 is not installed on the system. Changes for package SUNWsshcu will not be applied to the system.
Package SUNWsshu from directory SUNWsshu in patch 142910-17 is not installed on the system. Changes for package SUNWsshu will not be applied to the system.
Package SUNWgrubS from directory SUNWgrubS in patch 142910-17 is not installed on the system. Changes for package SUNWgrubS will not be applied to the system.
Package SUNWzoner from directory SUNWzoner in patch 142910-17 is not installed on the system. Changes for package SUNWzoner will not be applied to the system.
Package SUNWmdb from directory SUNWmdb in patch 142910-17 is not installed on the system. Changes for package SUNWmdb will not be applied to the system.
Package SUNWpool from directory SUNWpool in patch 142910-17 is not installed on the system. Changes for package SUNWpool will not be applied to the system.
Package SUNWudfr from directory SUNWudfr in patch 142910-17 is not installed on the system. Changes for package SUNWudfr will not be applied to the system.
Package SUNWxcu4 from directory SUNWxcu4 in patch 142910-17 is not installed on the system. Changes for package SUNWxcu4 will not be applied to the system.
Package SUNWarc from directory SUNWarc in patch 142910-17 is not installed on the system. Changes for package SUNWarc will not be applied to the system.
Package SUNWtftp from directory SUNWtftp in patch 142910-17 is not installed on the system. Changes for package SUNWtftp will not be applied to the system.
Package SUNWaccu from directory SUNWaccu in patch 142910-17 is not installed on the system. Changes for package SUNWaccu will not be applied to the system.
Package SUNWppm from directory SUNWppm in patch 142910-17 is not installed on the system. Changes for package SUNWppm will not be applied to the system.
Package SUNWtoo from directory SUNWtoo in patch 142910-17 is not installed on the system. Changes for package SUNWtoo will not be applied to the system.
Package SUNWcpc from directory SUNWcpc.i in patch 142910-17 is not installed on the system. Changes for package SUNWcpc will not be applied to the system.
Package SUNWftdur from directory SUNWftdur in patch 142910-17 is not installed on the system. Changes for package SUNWftdur will not be applied to the system.
Package SUNWypr from directory SUNWypr in patch 142910-17 is not installed on the system. Changes for package SUNWypr will not be applied to the system.
Package SUNWlxr from directory SUNWlxr in patch 142910-17 is not installed on the system. Changes for package SUNWlxr will not be applied to the system.
Package SUNWdcar from directory SUNWdcar in patch 142910-17 is not installed on the system. Changes for package SUNWdcar will not be applied to the system.
Package SUNWnfssu from directory SUNWnfssu in patch 142910-17 is not installed on the system. Changes for package SUNWnfssu will not be applied to the system.
Package SUNWpcmem from directory SUNWpcmem in patch 142910-17 is not installed on the system. Changes for package SUNWpcmem will not be applied to the system.
Package SUNWlxu from directory SUNWlxu in patch 142910-17 is not installed on the system. Changes for package SUNWlxu will not be applied to the system.
Package SUNWxcu6 from directory SUNWxcu6 in patch 142910-17 is not installed on the system. Changes for package SUNWxcu6 will not be applied to the system.
Package SUNWpcmci from directory SUNWpcmci in patch 142910-17 is not installed on the system. Changes for package SUNWpcmci will not be applied to the system.
Package SUNWarcr from directory SUNWarcr in patch 142910-17 is not installed on the system. Changes for package SUNWarcr will not be applied to the system.
Package SUNWscpu from directory SUNWscpu in patch 142910-17 is not installed on the system. Changes for package SUNWscpu will not be applied to the system.
Package SUNWcpcu from directory SUNWcpcu in patch 142910-17 is not installed on the system. Changes for package SUNWcpcu will not be applied to the system.
Package SUNWopenssl-include from directory SUNWopenssl-include in patch 142910-17 is not installed on the system. Changes for package SUNWopenssl-include will not be applied to the system.
Package SUNWdtrp from directory SUNWdtrp in patch 142910-17 is not installed on the system. Changes for package SUNWdtrp will not be applied to the system.
Package SUNWhermon from directory SUNWhermon in patch 142910-17 is not installed on the system. Changes for package SUNWhermon will not be applied to the system.
Package SUNWpsm-lpd from directory SUNWpsm-lpd in patch 142910-17 is not installed on the system. Changes for package SUNWpsm-lpd will not be applied to the system.
Package SUNWdtrc from directory SUNWdtrc in patch 142910-17 is not installed on the system. Changes for package SUNWdtrc will not be applied to the system.
Package SUNWhea from directory SUNWhea in patch 142910-17 is not installed on the system. Changes for package SUNWhea will not be applied to the system.
Package SUNW1394 from directory SUNW1394 in patch 142910-17 is not installed on the system. Changes for package SUNW1394 will not be applied to the system.
Package SUNWrds from directory SUNWrds in patch 142910-17 is not installed on the system. Changes for package SUNWrds will not be applied to the system.
Package SUNWnfsskr from directory SUNWnfsskr in patch 142910-17 is not installed on the system. Changes for package SUNWnfsskr will not be applied to the system.
Package SUNWudf from directory SUNWudf in patch 142910-17 is not installed on the system. Changes for package SUNWudf will not be applied to the system.
Package SUNWixgb from directory SUNWixgb in patch 142910-17 is not installed on the system. Changes for package SUNWixgb will not be applied to the system.
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
142910-17
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Patch 142910-17 has been successfully installed.
See /a/var/sadm/patch/142910-17/log for details
Executing postpatch script...
Creating GRUB menu in /a
Installing grub on /dev/rdsk/c2t0d0s0
stage1 written to partition 0 sector 0 (abs 16065)
stage2 written to partition 0, 273 sectors starting at 50 (abs 16115)
Patch packages installed:
BRCMbnx
SUNWaac
SUNWahci
SUNWamd8111s
SUNWcakr
SUNWckr
SUNWcry
SUNWcryr
SUNWcsd
SUNWcsl
SUNWcslr
SUNWcsr
SUNWcsu
SUNWesu
SUNWfmd
SUNWfmdr
SUNWgrub
SUNWhxge
SUNWib
SUNWigb
SUNWintgige
SUNWipoib
SUNWixgbe
SUNWmdr
SUNWmegasas
SUNWmptsas
SUNWmrsas
SUNWmv88sx
SUNWnfsckr
SUNWnfscr
SUNWnfscu
SUNWnge
SUNWnisu
SUNWntxn
SUNWnv-sata
SUNWnxge
SUNWopenssl-libraries
SUNWos86r
SUNWpapi
SUNWpcu
SUNWpiclu
SUNWpsdcr
SUNWpsdir
SUNWpsu
SUNWrge
SUNWrpcib
SUNWrsgk
SUNWses
SUNWsmapi
SUNWsndmr
SUNWsndmu
SUNWtavor
SUNWudapltu
SUNWusb
SUNWxge
SUNWxvmpv
SUNWzfskr
SUNWzfsr
SUNWzfsu
PBE GRUB has no capability information.
PBE GRUB has no versioning information.
ABE GRUB is newer than PBE GRUB. Updating GRUB.
GRUB update was successfull.
Unmounting the BE <s10x_u8wos_08a_Jan2011>.
The patch add to the BE <s10x_u8wos_08a_Jan2011> completed.
Still need to know how to resolve it though...

Created zone with defaults won't boot completely (Solaris 10, Update 1)

If I create a zone with defaults, i.e. allowing the zone to inherit the typical package dirs, the resulting zone does not boot completely. When I attach to the zone via zlogin, the zone looks to be in an administrative state. It never boots to a point where one would typically enter in the initial configuration info, e.g. timezone and root password.
However if I create the zone after first removing the inherited dirs, the zone boots to a state where it subsequently can be confiured and fully booted.
Looks as if the SMF facilities are not fully initialized when the zone is configured to inherit its packages. This could be a red herring as I'm a newbie who's moved over from Linux and starting to understand SMF specifically and Solaris in general.
I did not have this problem with Solaris 10. I've just installed Solaris 10 Update 1; the problem seems specific to that installation. I reinstalled and the problem persists.

I snipped the output because there were some errors, which on retrospect seems to have been a silly decision. I repeated the process and captured the missing output:
# zoneadm -z foo install
Preparing to install zone <foo>.
Creating list of files to copy from the global zone.
Copying <5913> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <942> packages on the zone.
Initialized <942> packages on zone.
Zone <foo> is initialized.
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWxwfnt
SUNWxwplt SUNWxwcft SUNWjxmft SUNWxwpls SUNWpmowu
SUNWxilrl SUNWolrte SUNWi13rf SUNWi15rf SUNWi2rf SUNWi5rf
SUNWi7rf SUNWi9rf SUNWtxfnt SUNWdoc SUNWi1of SUNWi4rf
SUNWi8rf SUNW1251f SUNWarrf SUNWxwoft SUNWxwxst
SUNWkoi8f SUNWasu SUNWxrpcrt SUNWasac SUNWasdb
SUNWasut>
The file </zone/foo/root/var/sadm/system/logs/install_log> contains a log of the zone installation.The packages are related to App development and X11. I don't see any that might be related to SMF.
The logfile is too large to post at over 37K lines. However there seemed to be a pattern to the package failures. Hopefully these greps highlight the important messages:
# grep "partially failed" /zone/foo/root/var/sadm/system/logs/install_log
Installation of <SUNWxwfnt> on zone <foo> partially failed.
Installation of <SUNWxwplt> on zone <foo> partially failed.
Installation of <SUNWxwcft> on zone <foo> partially failed.
Installation of <SUNWjxmft> on zone <foo> partially failed.
Installation of <SUNWxwpls> on zone <foo> partially failed.
Installation of <SUNWpmowu> on zone <foo> partially failed.
Installation of <SUNWxilrl> on zone <foo> partially failed.
Installation of <SUNWolrte> on zone <foo> partially failed.
Installation of <SUNWi13rf> on zone <foo> partially failed.
Installation of <SUNWi15rf> on zone <foo> partially failed.
Installation of <SUNWi2rf> on zone <foo> partially failed.
Installation of <SUNWi5rf> on zone <foo> partially failed.
Installation of <SUNWi7rf> on zone <foo> partially failed.
Installation of <SUNWi9rf> on zone <foo> partially failed.
Installation of <SUNWtxfnt> on zone <foo> partially failed.
Installation of <SUNWdoc> on zone <foo> partially failed.
Installation of <SUNWi1of> on zone <foo> partially failed.
Installation of <SUNWi4rf> on zone <foo> partially failed.
Installation of <SUNWi8rf> on zone <foo> partially failed.
Installation of <SUNW1251f> on zone <foo> partially failed.
Installation of <SUNWarrf> on zone <foo> partially failed.
Installation of <SUNWxwoft> on zone <foo> partially failed.
Installation of <SUNWxwxst> on zone <foo> partially failed.
Installation of <SUNWkoi8f> on zone <foo> partially failed.
Installation of <SUNWasu> on zone <foo> partially failed.
Installation of <SUNWxrpcrt> on zone <foo> partially failed.
Installation of <SUNWasac> on zone <foo> partially failed.
Installation of <SUNWasdb> on zone <foo> partially failed.
Installation of <SUNWasut> on zone <foo> partially failed.and# grep "not installed" /zone/foo/root/var/sadm/system/logs/install_log
*** package <SPROmrdwf> was not installed:
*** package <SPROdwrfb> was not installed:
*** package <SPROlang> was not installed:
*** package <SPROlangx> was not installed:
*** package <SPROdwrfx> was not installed:
*** package <SPROsbld> was not installed:
*** package <SPROsbldx> was not installed:
*** package <SPROrdbkb> was not installed:
*** package <SPROrdbkx> was not installed:
*** package <SPROcc> was not installed:
*** package <SPROutool> was not installed:
*** package <SPROmrcc> was not installed:
*** package <SPROmrcom> was not installed:
*** package <SPROmr3m> was not installed:
*** package <SPROmrtcv> was not installed:
*** package <SPROm9xs> was not installed:
*** package <SPROsunms> was not installed:
*** package <SPROsmsx> was not installed:
*** package <SPROsmpx> was not installed:
*** package <SPROmrsbe> was not installed:
*** package <SPROsbe> was not installed:
*** package <SPROpnsn> was not installed:
*** package <SPROfd> was not installed:
*** package <SPROupdck> was not installed:
*** package <SPROcpl> was not installed:
*** package <SPROcplx> was not installed:
*** package <SPROcmpl> was not installed:
*** package <SPROtlbn7> was not installed:
*** package <SPROtll7> was not installed:
*** package <SPROtl7x> was not installed:
*** package <SPROtll7x> was not installed:
*** package <SPROscl> was not installed:
*** package <SPROsclx> was not installed:
*** package <SPROmrstd> was not installed:
*** package <SPROmrcpl> was not installed:
*** package <SPROstl4h> was not installed:
*** package <SPROstl4a> was not installed:
*** package <SPROstl4o> was not installed:
*** package <SPROstl4x> was not installed:
*** package <SPROstl4y> was not installed:
*** package <SPROftool> was not installed:
*** package <SPROl90> was not installed:
*** package <SPROl90x> was not installed:
*** package <SPROl90s> was not installed:
*** package <SPROl90sx> was not installed:
*** package <SPROf90> was not installed:
*** package <SPROmrftn> was not installed:
*** package <SPROgc> was not installed:
*** package <SPROlgc> was not installed:
*** package <SPROgcx> was not installed:
*** package <SPROlgcx> was not installed:
*** package <SPROdbx> was not installed:
*** package <SPROdbxx> was not installed:
*** package <SPROjdbx> was not installed:
*** package <SPROjdbxx> was not installed:
*** package <SPROmrdbx> was not installed:
*** package <SPROdemo> was not installed:
*** package <SPROdmake> was not installed:
*** package <SPROmrdmk> was not installed:
*** package <SPROtdemo> was not installed:
*** package <SPROmride> was not installed:
*** package <SPROdbxui> was not installed:
*** package <SPROsvc> was not installed:
*** package <SPROxdplg> was not installed:
*** package <SPROidext> was not installed:
*** package <SPROjnsnb> was not installed:
*** package <SPROjnsrt> was not installed:
*** package <SPROjnsup> was not installed:
*** package <SPROctags> was not installed:
*** package <SUNWnbide> was not installed:
*** package <SUNWnbcpp> was not installed:
*** package <SUJAnbcpp> was not installed:
*** package <SUZHnbcpp> was not installed:
*** package <SUNWexted> was not installed:
*** package <SUJAexted> was not installed:
*** package <SUZHexted> was not installed:
*** package <SPROnbreg> was not installed:
*** package <SPROfdxd> was not installed:
*** package <SPROmrxd> was not installed:
*** package <SPROgvim> was not installed:
*** package <SPROxmbin> was not installed:
*** package <SPROxmshr> was not installed:
*** package <SPROxmsrc> was not installed:
*** package <SPROmrxm> was not installed:
*** package <SPROprfan> was not installed:
*** package <SPROmrpan> was not installed:
*** package <SPROprfax> was not installed:
*** package <SPROprflb> was not installed:
*** package <SPROprflx> was not installed:
*** package <SPROprfgn> was not installed:
*** package <SPROmrpgn> was not installed:
*** package <SPROhtbas> was not installed:
*** package <SPROhttl7> was not installed:
*** package <SPROhtstd> was not installed:
*** package <SPROhtxd> was not installed:
*** package <SPROdwrfs> was not installed:
*** package <SPROrdbks> was not installed:
*** package <SPROctsrc> was not installed:
*** package <SPROplg> was not installed:
*** package <SPROpl> was not installed:
*** package <SPROplx> was not installed:
*** package <SPROpls> was not installed:
*** package <SPROplsx> was not installed:
*** package <SPROmrpl> was not installed:These messages seem to be inline with the general output captured from the zone install itself.
> What does "svcadm list -vc" give you when you started the zone ?
I took that as a typo, instead using "zoneadm?"
# zoneadm list -vc
ID NAME             STATUS         PATH
   0 global           running        /
   7 foo              running        /zone/fooThe zone is not on its own slice, however "/zone" is mounted as a loopback from /export/zone. I don't think that's a problem since the zone install seems to work if I don't inherit packages. Unless perhaps its a nesting level of lofs's.
FWIW,
# mount |grep zone
/zone on /export/zone read/write/setuid/devices/dev=1540000 on Fri Feb 24 16:10:55 2006
/zone/foo/root/dev on /zone/foo/dev read/write/setuid/devices/zonedevfs/dev=4640007 on Tue Feb 28 13:13:03 2006
/zone/foo/root/lib on /lib read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/platform on /platform read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/sbin on /sbin read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/usr on /usr read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/proc on proc read/write/setuid/nodevices/zone=foo/dev=4400007 on Tue Feb 28 13:13:06 2006
/zone/foo/root/system/contract on ctfs read/write/setuid/nodevices/zone=foo/dev=43c0008 on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/svc/volatile on swap read/write/setuid/nodevices/xattr/zone=foo/dev=448000e on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/mnttab on mnttab read/write/setuid/nodevices/zone=foo/dev=4440008 on Tue Feb 28 13:13:06 2006

Help only displays the frame in Solaris 10, update 6

I have a help application that has been running fine since Solaris 8. It works in Solaris 10, update 1, but not in update 6. Only an empty help frame is displayed. My JRE is 1.6.0_05-b13, and I am using help 1.1.13. I suspect that replacing the default HelpUI with my own subclass has stopped working. My application has this line of code which is used to replace the default HelpUI:
UIManager.getDefaults().put("HelpUI", "HelpUIWithClose");
The users wanted a close button, so HelpUIWithClose is subclassed from BasicHelpUI, and a big close button is added on the toolbar. This has been working for years. Before and after this line of code are two print statements that get the toString value of the UIDefaults HelpUI object. The results are:
(before)
javax.help.plaf.basic.BasicHelpUI
(after)
HelpUIWithClose
I am only guessing at the problem because of all of the "Unknown Source" values in the trace below. If I comment out the UIManager line above that replaces HelpUI with HelpUIWithClose, the help functions normally, but of course it is missing the close button added by HelpUIWithClose.
An alternate question might be how to add a close button to the toolbar of help?
I get a very long trace when this fails. I will post it at the end of this email. Any ideas on what is wrong?
Thanks,
Herb Miller
UIDefaults.getUI() failed: no ComponentUI class for: javax.help.JHelp[,0,0,0x0,invalid,alignmentX=0.0,alignmentY=0.0,border=,flags=0,maximumSize=,minimumSize=,preferredSize=]
java.lang.Error
at javax.swing.UIDefaults.getUIError(Unknown Source)
at javax.swing.MultiUIDefaults.getUIError(Unknown Source)
at javax.swing.UIDefaults.getUI(Unknown Source)
at javax.swing.UIManager.getUI(Unknown Source)
at javax.help.JHelp.updateUI(JHelp.java:299)
at javax.help.JHelp.<init>(JHelp.java:121)
at javax.help.WindowPresentation.createJHelp(WindowPresentation.java:843)
at javax.help.WindowPresentation.createHelpWindow(WindowPresentation.java:879)
at javax.help.WindowPresentation.setDisplayed(WindowPresentation.java:346)
at javax.help.DefaultHelpBroker.setDisplayed(DefaultHelpBroker.java:178)
at javax.help.CSH.displayHelp(CSH.java:749)
at javax.help.CSH.access$200(CSH.java:80)
at javax.help.CSH$DisplayHelpFromSource.actionPerformed(CSH.java:1668)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

Never mind.
It is a known bug documented on manual " [Solaris 10 10/08 Release Notes, Chapter 2 Solaris Runtime Issues|http://docs.sun.com/app/docs/doc/820-5245/chapter2-1000?a=view] " as shown below.
The solution is to apply vold patch [138130-01|http://sunsolve.sun.com/search/document.do?assetkey=1-21-138130-01-1].
Solaris 10 10/08 DVD Media Might Not be Automatically Mounted by vold (6712352)
The Solaris 10 10/08 DVD does not mount by default during runtime. No error message is displayed.
Workaround: Perform the following steps:
   1. Become superuser.
   2. Disable vold:
      * On Solaris 10 Systems:
            # svcadm disable -t volfs
      * On Solaris 8 and Solaris 9 systems:
            /etc/init.d/volmgt stop
   3. Mount the media manually by using the # mount -F hsfs path to block device path to mount point command. For example:
      # mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt

So, noone at all is running SJS Web Server on Solaris 10 Update 6??

Trying to get some feedback on running SJS Web Server under Solaris 10 Update 6.
problems?
"Boy, That was a Mistake"
"Works Great"
"No Problems"
What?? Anything at all...
Thanks

Never mind.
It is a known bug documented on manual " [Solaris 10 10/08 Release Notes, Chapter 2 Solaris Runtime Issues|http://docs.sun.com/app/docs/doc/820-5245/chapter2-1000?a=view] " as shown below.
The solution is to apply vold patch [138130-01|http://sunsolve.sun.com/search/document.do?assetkey=1-21-138130-01-1].
Solaris 10 10/08 DVD Media Might Not be Automatically Mounted by vold (6712352)
The Solaris 10 10/08 DVD does not mount by default during runtime. No error message is displayed.
Workaround: Perform the following steps:
   1. Become superuser.
   2. Disable vold:
      * On Solaris 10 Systems:
            # svcadm disable -t volfs
      * On Solaris 8 and Solaris 9 systems:
            /etc/init.d/volmgt stop
   3. Mount the media manually by using the # mount -F hsfs path to block device path to mount point command. For example:
      # mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt

Postgresql service 8.2 on Solaris 10 Update 4

Hi
I have solaris 10 update 4 installed. PostgreSQL with SMF is shipped with Solaris 10 update 4.
I could see two services installed on the OS.
svcs postgresql
disabled 14:58:36 svc:/application/database/postgresql:version_81
maintenance 15:40:42 svc:/application/database/postgresql:version_82
I followed the steps to start postgres service given on Sun website...
PostgreSQL 8.2:
1. As root, su to postgres:
# su - postgres
2. Create PostgreSQL DB cluster:
$ /usr/postgres/8.2/bin/initdb -D /var/postgres/8.2/data
3. As root, use the SMF's svcadm command to start PostgreSQL:
# /usr/sbin/svcadm enable postgresql:version_82
now I could see one serive enabled.
svcs postgresql
disabled 14:58:36 svc:/application/database/postgresql:version_81
online 15:40:42 svc:/application/database/postgresql:version_82
But, when I disabled the service & restarted it using...
svcadm disable svc:/application/database/postgresql:version_82
svcadm enable svc:/application/database/postgresql:version_82
I see the serivce in the maintenance mode.
disabled 14:58:36 svc:/application/database/postgresql:version_81
maintenance 15:40:42 svc:/application/database/postgresql:version_82
Server.log shows following error:-
FATAL: syntax error in file "/var/postgres/8.2/data/postgresql.conf" line 104, near token "MB"
Can anyone help me know the reason?
Thanx in advance
Niraj

Hi
I have solaris 10 update 4 installed. PostgreSQL with SMF is shipped with Solaris 10 update 4.
I could see two services installed on the OS.
svcs postgresql
disabled 14:58:36 svc:/application/database/postgresql:version_81
maintenance 15:40:42 svc:/application/database/postgresql:version_82
I followed the steps to start postgres service given on Sun website...
PostgreSQL 8.2:
1. As root, su to postgres:
# su - postgres
2. Create PostgreSQL DB cluster:
$ /usr/postgres/8.2/bin/initdb -D /var/postgres/8.2/data
3. As root, use the SMF's svcadm command to start PostgreSQL:
# /usr/sbin/svcadm enable postgresql:version_82
now I could see one serive enabled.
svcs postgresql
disabled 14:58:36 svc:/application/database/postgresql:version_81
online 15:40:42 svc:/application/database/postgresql:version_82
But, when I disabled the service & restarted it using...
svcadm disable svc:/application/database/postgresql:version_82
svcadm enable svc:/application/database/postgresql:version_82
I see the serivce in the maintenance mode.
disabled 14:58:36 svc:/application/database/postgresql:version_81
maintenance 15:40:42 svc:/application/database/postgresql:version_82
Server.log shows following error:-
FATAL: syntax error in file "/var/postgres/8.2/data/postgresql.conf" line 104, near token "MB"
Can anyone help me know the reason?
Thanx in advance
Niraj

Warning fail to update schema entries (iDA)

Installation of iDA generates the following log (setup.log):
- [iDA] Info iDA Pre-Installation Starts ....
- [iDA] Info iDA setup log file is /export/home/servers/ida/setup/nda-setup.log
- [iDA] Info iDA Post-Installation Starts...
- [iDA] Warning fail to update schema entries (iDA) in directory server
- [iDA] Info About to Add NDAUser ACI to UserSuffix
- [iDA] Info About to Add NDAUser ACI to DCRoot
- [iDA] Info log additional files to the uninstall log
So far I was not able to determine the origin of the warning. Moreover, when I try to
run db2ldif with -s internet (supposed to be my DC tree), the system returns the
following messages:
- Backend Instance: internetdb
- warning: entrydn not indexed on 'internet'
- Failed to fetch subtree lists (error -30991) DB_NOTFOUND: No matching key/data pair found
- Possibly the entrydn or ancestorid index is corrupted or does not exist.
- Attempting direct unindexed export instead.
- export internetdb: Processed 4 entries (100%).
Some of the parameter used when installing all products include:
Admin Domain = Default Domain = siroe.com.br
Org Suffix = UserGroup Suffix = User Data Suffix = dc=siroe,dc=com,dc=br
Default Org DN: [o=siroe.com.br, dc=siroe, dc=org, dc=br] (default option; only possible choice: will not work otherwise)
without installing iDA info: yes
DC Suffix: o=internet
NOTE: I believe I've gone thru all the recommendations already present in this Forum
Dear fellows,
can you help me clear this situation?
TIA
Ivo

Hi RichD Miller,
Based on my understanding, you got the error shown in your post when you tried to update the schema for Active Directory. Right?
According to the error message, there maybe a syntax error in the input file. Please help to collect the following information for future troubleshooting:
How did you update the schema?
Did you update the schema in GC? If not, please try in GC.
For your information, please refer to the following article to get more help:
Active Directory Schema Update
Using LDIFDE to import and export directory objects to Active Directory
Regards,
Lany Zhang

New to solaris---is update manager working correctly?

well as my subject says I am new to solaris having put it on an pc bout a week ago. as I am using the "free" verson (not open solaris) I knew I would not be entitled to certain goodies but seem to have run into an issue getting the updates I (presumably) am entitled to. simply put I open up the solaris application "update manager" which is on my desktop saying "updates available". now upon initially launching the app I specified that I was using the free version (well it let me register without a code so I assume sun knows my status), and then selected the option to put a check mark next to all available updates. well after waiting like a full day with it showing that is was still in the process up updating I eventually aborted the process. I then tried installing a couple of the updates and though it took a while it worked. so I selected 3 of 4 more and again the update manager showed that I was updating but nothing was happening (to my knowledge). after several hours I aborted the app again. so what am I doing wrong. first off I am assuming that what sun presents to me is what is actually available to me using the free unregistered version of solaris. why then would updates fail? btw I know some linux (not an expert) and I figured that behind the scenes update manager was checking for dependencies and installing what I needed from sun repos. but of course I could be way off bass here. so what gives? thanks much in advance.

first off I am assuming that what sun presents to me is what is actually available to me using the free unregistered version of solaris.No. Update Manager will show you everything but will only allow you to install basically security and a small subset of other patches.
When you ran through the Solaris registration GUI you had a chance to enter a support contract #. If you chose not to enter one or if you want to use it without registering then you only get access to a few of the patches.
alan

RMMR1MRS-When run in background cause update failure errors looking

hi,
RMMR1MRS report when run in background cause update failure errors .
There are few below reason for the error log.
1. for the PO invoice already generated - (its right if already invoice generated. should not happen again)
2. In MIGO, entire quantity has been reversed and also invoice generated with zero value - ( its right , should not happen invoice again )
3. Particular PO line item deleted - (its right if the PO line item deleted. ERS settlement not require)
For the all above reason, the update error occurs. But the mean time the program "RMMR1MRS" should not through the update error log.
Note: The job was not terminated due to this update error and also no harm because of the error log
can you please help on this update failure why it occurs.

Have you found a solution already? If so, please, share it with the community and close this thread.

I started my update for ios 5.1for iPhone 4s and cancelled it have way through now it says it's downloaded but really it's not the update is still there and when I try to update it it says unable to install update : an error occurred installing iOS 5.1 ?

I started my update for ios 5.1for iPhone 4s and cancelled it have way through now it says it's downloaded but really it's not the update is still there and when I try to update it it says unable to install update : an error occurred installing iOS 5.1 ?

See Here... Unable to Update or Restore...
http://support.apple.com/kb/HT1808

"software update" "An error occurred while checking for updates"

When I click on "Software Update", an error results, "An error occurred while checking for updates". It is definitely connected to the internet. I was gifted a G5 and I installed a new hard drive and loaded the OS, OS X 10.3.5. That version of Safari does not display pages correctly. E.g., support.apple.com/downloads just clocks on the righthand side of the page.
Because cannot access that link, cannot manually update the OS - I was thinking this version is "old" and as a result, unable to connect to apple's update server. Thanks.

Thanks, I upgraded with your info.
Ultimately, I am trying to access mail.google.com but receiving the following error with opera v9.5.x: Some important features may not work in this version of your browser, so you have been redirected to the Basic HTML version.
Safari gives the following: Some important features may not work in this version of your browser, so you have been redirected to the Basic HTML version.
I can access ask.com and using opera to type this response.

Idsconfig/Solaris 9:update schema error

Similar Messages

Maybe you are looking for