From: Aleksey Novodvorsky <aen@logic.ru>
To: mandrake-russian@altlinux.ru
Subject: Re: [mdk-re] Oracle8i + Spring2001
Date: Wed Jul 18 01:44:10 2001
Message-ID: <3B54812D.42E1D1AB@logic.ru> (raw)
In-Reply-To: <000601c10f02$d8b24ec0$8e44efc3@duke>
"Alexey N. Titov" wrote:
> Точно такая же проблема и у меня --
> куча core - файлов в $ORACLE_HOME/dbs
> ----- Original Message -----
> From: Boyko Vadim
> To: mandrake-russian@altlinux.ru
> Sent: Monday, July 16, 2001 3:22 AM
> Subject: [mdk-re] Oracle8i + Spring2001
>
> Всем здрасте!
>
> Кто-нибудь соединил вместе subj?
> Очень надо, не ставить же шапочку обратно, где все работало?
> Я уже спрашивал, но в ответ тишина.
> Oracle сам ставится, а как доходит до создания базы
> вешается.
> $>svmgrl
> ...
> connect internal -> connected
> startup nomount ... -> и все замирает а в $ORACLE_HOME/dbs
> создаются каталоги core...
> Все что было написано в доке по установке я сделал,
> да и раньше все проходило нормально, но под шапочкой.
> kernel 2.2.18ipl5mdk... мозгов 256 P-III600
>
> Если у кого это работает буду рыть дальше, а если нет
> то прощай Весна 2001, придется восстанавливать шапочку.
> Не для развлечений надо, для работы.
>
> Спасибо за любой ответ, можно на мыло если считаете это оф-топиком.
>
Господа, а вот это вы читали? :
atch Description
-----------------
Oracle8i for Linux is shipped with archived
objects which were compiled using
glibc-2.1.3. The executable components are
then linked at install-time using
these archives. Due to compatibility
limitations in glibc, if the target
system for an installation is based on a
later version of glibc, then the
executables produced by the linker will not
be valid. As a workaround to
this limitation, we have created a set of
stub libraries which are used at
link-time only to mimic the contents of
glibc-2.1.3 shared objects. Note
that these stub libraries do not contain
valid executable code, and therefore
*must NOT* be included in the library path
searched by the dynamic loader
(i.e., do not include $ORACLE_HOME/lib/stubs
in LD_LIBRARY_PATH).
===========================================
Instructions for New Oracle8i Installations
-------------------------------------------
Install Oracle8i as usual, but choose not to
create a database during install.
Once installation is complete, follow the
procedure described in the
section "Instructions for Existing
Installations" below. It will then
be possible to create a database.
================================================
Instructions for Existing Oracle8i
Installations
------------------------------------------------
Place the tar file glibc-2.1.3-stubs.tar.gz
in $ORACLE_HOME. Make sure
ORACLE_HOME is set in your environment. Then
carry out the following steps:
cd $ORACLE_HOME
tar xvfz glibc-2.1.3-stubs.tar.gz
./setup_stubs.sh
You should now be able to use Oracle as
usual.
================
Warning
----------------
Make sure the directory $ORACLE_HOME/lib is
not listed in your
/etc/ld.so.conf. The system could
potentially become unstable after applying
this patch in that case. If $ORACLE_HOME/lib
is currently listed in
/etc/ld.so.conf, remove it and run ldconfig
before applying this patch.
================================
Notes for Application Developers
--------------------------------
If your application does not require linking
at install sites, then no
additional steps are required for your
application to be compatible with
glibc or the Oracle8i client shared library
after the installation of this
patch. This is true regardless of whether
your application was compiled
using glibc-2.1.3 or a later version.
If your application is compiled using
glibc-2.1.3 and requires linking at
install-time using the Oracle8i client
shared library, then you may also
need to link your application using the stub
libraries provided in this
patch. For example, an application which
might typically be linked as
follows on a glibc-2.1.3 based system:
gcc -o app app.o -L$ORACLE_HOME/lib -lclntsh
should now be linked as follows on systems
with a newer version of glibc,
in order to ensure compatibility:
gcc -o app app.o -L$ORACLE_HOME/lib
-L$ORACLE_HOME/lib/stubs -lclntsh
If your application is compiled using a
version of glibc later than 2.1.3
and requires linking at install-time using
the Oracle8i client shared
library, then you must NOT link your
application with the stub libraries
provided in this patch. Doing so may either
cause the link to fail or the
resulting executables to be invalid.
Note that the stub libraries provided in
this patch only cover the shared
objects that make up glibc. If your
application must be linked at install-
time with other shared objects which were
built to have dependencies on the
locally installed version of glibc (e.g.,
X11), then your application must
be compiled using the same version of glibc
that was used by those other
components. For example, on a system with
glibc-2.2, linking your
application with libX11.so will fail if you
attempt to use the glibc-2.1.3
stub libraries, since libX11.so on that
system will have been compiled and
linked using glibc-2.2.
================
Revision History
----------------
06-FEB-2001: added ldconfig warning to
README
08-FEB-2001: added libnsl.so stub needed for
OPS cm/nm
28-FEB-2001: move stub libraries from
$OH/lib to $OH/lib/stubs
01-MAR-2001: added stubs for all remaining
glibc libraries
14-MAR-2001: added setup_stubs.sh to
simplify installation
16-MAR-2001: added patch description and
notes for application developers
-------------
URL:
http://otn.oracle.com/software/products/oracle8i/files/READMEglib213.html
Но нужна регистрация. Если у вас проблемы с регистрацией, -- напишите
мне лично.
Rgrds, AEN
prev parent reply other threads:[~2001-07-18 1:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 2:07 ` Aleksey Novodvorsky
2001-07-16 2:18 ` Boyko Vadim
2001-07-16 15:12 ` dsv
2001-07-18 0:41 ` Alexey N. Titov
2001-07-18 1:44 ` Aleksey Novodvorsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B54812D.42E1D1AB@logic.ru \
--to=aen@logic.ru \
--cc=mandrake-russian@altlinux.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Community general discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
public-inbox-index community
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.community
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git