Assembler "/usr/ccs/bin/as" error while running Oracle 11G upgrade script
underh20
errors when upgrading the Oracle to 11G-R2. Any idea how I can resolve
this ? Is this have anything to do with the version of Solaris 10
which is (01/06) ?
**********************************************************************************************************
INFO: /usr/ccs/bin/as
INFO: : error: unknown option '6'
/usr/ccs/bin/as: error: unknown option '4'
usage: /usr/ccs/bin/as [-V] [-Q{y,n}] [-q] [-s]
[-S] [-K {pic,PIC}] [-o objfile] [-L] [-T]
[-P [[-Yc,path] [-Ipath] [-Dname] [-Dname=def] [-Uname]]...]
[-m [-Ym,path]] [-n] [-ul] [-xF] [-xarch=
{v7,v8,v8a,v8plus,v8plusa,v8plusb,v9,v9a,v9b}] [-xcode={pic13,pic32}]
file.s...
INFO: make: Fatal error: Command failed for target `ntcontab.o'
INFO: *** Error code 1
**********************************************************************************************************
The script seems to be pointing to the wrong assembler "as" at this
server.
Should we be using the gcc in "/usr/sfw/bin" exclusively for the
Oracle 11G upgrade script ? Thanks, Bill
atlantis> which gcc
/usr/local/bin/gcc
atlantis> ls -lt /usr/local/bin/gcc
-rwxr-xr-x 1 root other 187348 Sep 6 2000 /usr/local/bin/
gcc
atlantis> ls -lt /usr/sfw/bin/gcc
-r-xr-xr-x 3 root bin 122260 Jan 22 2005 /usr/sfw/bin/gcc
atlantis> /usr/local/bin/gcc -v
Using builtin specs.
gcc version 2.8.1
atlantis> /usr/sfw/bin/gcc -v
Reading specs from /usr/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.3/specs
Configured with: /gates/sfw10/builds/sfw10-gate/usr/src/cmd/gcc/
gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --
with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-
languages=c,c++ --enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
Frank Langelage
> Our server is running Solaris 10 (01/06). We are getting following
> errors when upgrading the Oracle to 11G-R2. Any idea how I can resolve
> this ? Is this have anything to do with the version of Solaris 10
> which is (01/06) ?
>
You don't need a C-compiler, only assembler and linker are needed.
Look into install/make.log
On my system (Solaris 10 6/06 with all available patches applied) there
are the following lines:
/opt/oracle/11gR2/bin/gennttab > ntcontab.s ;\
/usr/ccs/bin/as -P *-m64* -o ntcontab.o ntcontab.s ;\
rm -f /opt/oracle/11gR2/lib/ntcontab.o ;\
mv ntcontab.o /opt/oracle/11gR2/lib/ ;\
/usr/ccs/bin/ar rv /opt/oracle/11gR2/lib/libn11.a
/opt/oracle/11gR2/lib/ntcontab.o ; fi)
ar: /opt/oracle/11gR2/lib/libn11.a wird geschrieben
r - ntcontab.o
So on your system the used assembler is the same but this version
doesn't understand the 64-bit option I guess.
root@sb2000: /usr/ccs/bin/as -V
/usr/ccs/bin/as: SunOS 5.10 118683-04 Patch 10/05/2009
root@sb2000: /usr/ccs/bin/as
/usr/ccs/bin/as: error: no input filename given
usage: /usr/ccs/bin/as [-V] [-Q{y,n}] [-q] [-s]
[-S] [-K {pic,PIC}] [-o objfile] [-L] [-T]
[-P [[-Yc,path] [-Ipath] [-Dname] [-Dname=def] [-Uname]]...]
[-m [-Ym,path]] [-n] [-ul] [-xF]
[-m32] *[-m64]*
[-xarch={v7,v8,v8a,v8plus,v8plusa,v8plusb,v9,v9a,v9b,sparc,sparcvis,
sparcvis2,sparcfmaf,sparcima}]
[-xcode={pic13,pic32}] file.s...
underh20
Thanks for Frank's earlier note.
I just issued the two commands below at our server. My output is
definitely from yours.
We don't have the patch #118683 as it didn't appear when we did the "-
V" option below.
The "/usr/ccs/bin/as" also doesn't have the " [-m32] *[-m64]*" in the
usage fields.
Do you have any idea how we can get the correct version of "/usr/ccs/
bin/as". Hope
we can stay with the current version of Solaris 10 i.e., 01/06 since
upgrade to
the latest version of 10/08 or above is not a version with the time
constraint.
# /usr/ccs/bin/as -V
/usr/ccs/bin/as: Sun Compiler Common 10 Patch 05/06/2005
#
# /usr/ccs/bin/as
/usr/ccs/bin/as: error: no input filename given
usage: /usr/ccs/bin/as [-V] [-Q{y,n}] [-q] [-s]
[-S] [-K {pic,PIC}] [-o objfile] [-L] [-T]
[-P [[-Yc,path] [-Ipath] [-Dname] [-Dname=def] [-Uname]]...]
[-m [-Ym,path]] [-n] [-ul] [-xF] [-xarch=
{v7,v8,v8a,v8plus,v8plusa,v8plusb,v9,v9a,v9b}] [-xcode={pic13,pic32}]
file.s...
#
Frank Langelage
>
>
> Thanks for Frank's earlier note.
>
> I just issued the two commands below at our server. My output is
> definitely from yours.
> We don't have the patch #118683 as it didn't appear when we did the "-
> V" option below.
> The "/usr/ccs/bin/as" also doesn't have the " [-m32] *[-m64]*" in the
> usage fields.
> Do you have any idea how we can get the correct version of "/usr/ccs/
> bin/as". Hope
> we can stay with the current version of Solaris 10 i.e., 01/06 since
> upgrade to
> the latest version of 10/08 or above is not a version with the time
> constraint.
>
you don't have to upgrade the whole system to a more current Solaris
release.
But you'll have to install a patch.
The options for 32-/64-bit where introduced with the /usr/ccs/bin/as in
patch 118683-02.
The current version of this patch is -04.
See http://sunsolve.sun.com/patchfinder/?patchId=118683.
As far as I could see there are no dependencies to other patches.
ravi
> On 07.01.10 21:04, underh20 wrote:
>
>
>
>
>
> > Thanks for Frank's earlier note.
>
> > I just issued the two commands below at our server. My output is
> > definitely from yours.
> > We don't have the patch #118683 as it didn't appear when we did the "-
> > V" option below.
> > The "/usr/ccs/bin/as" also doesn't have the " [-m32] *[-m64]*" in the
> > usage fields.
> > Do you have any idea how we can get the correct version of "/usr/ccs/
> > bin/as". Hope
> > we can stay with the current version of Solaris 10 i.e., 01/06 since
> > upgrade to
> > the latest version of 10/08 or above is not a version with the time
> > constraint.
>
> you don't have to upgrade the whole system to a more current Solaris
> release.
> But you'll have to install a patch.
> The options for 32-/64-bit where introduced with the /usr/ccs/bin/as in
> patch 118683-02.
> The current version of this patch is -04.
> As far as I could see there are no dependencies to other patches.
we also come across this situation, but we reinstalled OS with u6
version.
let us know once the above patch is resolved..