Poor Yum Repo: OracleLinux6

I’m now working on an Oracle Linux 6U1 x64 box, planning to inst new 11R2 image.

Problem hit here.

we can see that glibc.i686 <tip: just add arch. tag to install related pkg.> cannot be resolved  for glibc-common label check failure.

it’s funny but not worse, ORCL even doesn’t provide glibc-common.i686 package…
http://public-yum.oracle.com/repo/OracleLinux/OL6/1/base/x86_64/

It should be a bug here….

WorkAround:

1. pull glibc package from weburl glibc-2.12-1.25.el6.i686.rpm.
2. # yum localinstall glibc-2.12-1.25.el6.i686.rpm
3. # yum install unixODBC-devel unixODBC-devel.i686
4. continue…

Notes….
Poor Yum repo…especially on x64 platform day’s, mixing with i686 libs.

where is the whereis

Today when I’m applying some scripts on Solaris 11Express nodes, a interesting error comeup,

As on Solaris 10, we use cmd whereis(/usr/ucb/whereis) as a standard component.
(On Linux, it’s also a part of the util-linux-ng package )

Solaris 11X doesn’t include this command in default set, so turn to documents for help:

<Oracle Solaris 11 ISV Adoption Guide>

Very lucky the command whereis is the rest  for kept in compatibility/ucb package as optional.
But it’s no longer suggested to use such cmds in further SOLs, I finally gave up refresh the toolkits.

[Refrence:]
Oracle Solaris 11 ISV Adoption Guide
Solaris 11 Express Changes: Where is /usr/ucb ?
PSARC/2009/540*
*this arc shows the discussion on some port specific /usr/ucb commands,
the abandon of those codes speed up the far and away of those BSD like code.

From this point, SOL’s running faster than Linux….

ORA-28055: the password will expire within 7 days

hit this issue, under scott/tiger schema, fix, to change passwd

The more…

Double check the table dba_profiles, and to change password_life_time parameter if necessary

[PL/SQL Notes] PRAGMA AUTONOMOUS_TRANSACTION

自治事务,在PL/SQL语句内部执行。
在声明部分使用编译指示说明的,就标为自治,

嵌套块不可以声明为自治,
只有包中的单独子程序可以标记为自治,包本身不能标记自治。
or,PLS-710

java.io.FileNotFoundException: datamodeler.log on sqldeveloper

sqldeveloper reported warning on datamodeler.log.

after check on OS,the sqldeveloper failed to create logs for priviledge issues.