|
Setting the timezone on RedHat
Posted on 22 July 2002 02:00 | Permalink
To change the timezone on RedHat Linux (if you don't want to use timeconfig): Edit /etc/sysconfig/clock and chage the ZONE= line. Now copy the appropriate file out of /usr/share/zoneinfo/ to /etc/localtime. The date should be instantly updated.
Reader comments: 0
Sparc Processors
Posted on 21 July 2002 02:00 | Permalink
To see how many processors and of what speed on a Sparc system:
prtconf -vp | more
Reader comments: 0
Nice uptime
Posted on 20 July 2002 02:00 | Permalink
Ya just gotta love Linux:
Reader comments: 0
Another Oracle note
Posted on 15 July 2002 15:00 | Permalink
Another Oracle note. This note is related to metalink DocID 132904.1, which provides an import/export compatibility matrix for different versions of Oracle. I was attempting an export from a 9.2.0 database using the export tool from 8.1.6. According to this document this procedure should have worked fine. What it doesn't tell you is that along with the export utility from the lower version database you need the full client install (or at least more than just the executable itself) to make the export happen. Otherwise the export is bound to bail with ORA-00056. So you'll need to have the client install from the lower version on the same machine, or perhaps a client install from the lower version on another machine and run the export over Net8.
Reader comments: 1
Oracle on Linux
Posted on 15 July 2002 11:00 | Permalink
15 Jul, 2002. Today I installed Oracle 9.2.0 on a fairly stock RedHat Linux 7.2 machine. The main gotcha I ran into was setting the shmmax kernel parameter. It used to be that you had to rebuild your kernel to set that one, so I shied away from doing it, even though the docs said I needed to. But then I found that it was apparently as easy as echoing the value in to /proc/sys/kernel/shmmax. Oracle recommends setting it to half the amount of physical memory (Perhaps that became a /proc entry in 2.4.x???).
I was able to get through the install fine without making the change, but once I tried creating a database it was a no-go. I tried lowering the memory size of the db I was creating, as well as dropping the number of processes, as suggested in a metalink document, all of which had no effect. The database creation kept bailing out with an ORA-03113, until I made the change in /proc. Guess they mean it when they say you need to change it ;-)
Now, I haven't used this stuff in a production environment yet, but I can at least get the database started and perform exports/imports against it. YMMV.
Reader comments: 0
<- Prev 10 | Next 10 ->
|
