This is an issue that keeps tripping me up in the development lab.
I create a quick database, and then after some time I go back to try to log in, and get:
ORA-28002: the password will expire within 7 days
And then I spend a while trying to figure out how to disable the password expiry component of the profile.
Here then, for my benefit as much as anyone else, is my quick guide to checking the user profile, and then disabling security components that cause headaches in the development lab.
I have stated this before. I am not a lawyer.
Neither am I an investment expert. Heck I ploughed money into Transocean two months before the Deepwater Horizon sank to the bottom of the Gulf and left a destructive oily mess all over the Gulf Coast.
So don’t take any stock picks from me.
But on a recent trip to the Midwest I met with a customer in an interesting predicament.
It seemed a simple enough thing to need to do;
Use the Swingbench oewizard tool to generate 1TB of data in my test database on DSSD, using the lights-out mode.
I am guessing everyone else knows how to do this, but it wasn’t obvious to me! And after spending nearly thirty minutes online trying to figure out how to connect through JDBC thin drivers as a SYSDBA privileged account, I finally realized that you specify the SYS password, but you DON’T specify the SYS username
So for any other DBAs as dense as me; here is how to create a 1TB Swingbench SOE schema using the oewizard in lights-out mode:
./oewizard -cl -create -scale 1000 -u soe -p soe -ts soe -tc 96 -df +DATA -cs //localhost:1521/dssd04 -dt thin -part -allindexes -bigfile -dbap oracle
After indexes are added, the SOE tablespace will be about 2.2TB.
EMC recently announced the availability of its DSSD rack scale flash storage appliance.
DSSD’s specs are impressive:
- 10 Million IOPs
- 100GB/S bandwidth
- 144TB capacity
- 100uS latency
The DSSD D5 takes a different approach to flash storage, by eliminating the latency prone networking layer typically handled by Fibre Channel, Infiniband or iSCSI. DSSD replaces this with a PCI extension through a proprietary PCIe Isley Card that connects servers to the D5.
DSSD also replaces conventional SSDs that package NAND technology and makes them look like fast spinning disks, with Flash Modules that eliminate much of the latency of mimicking spinning disks.
There’s a lot more to the D5 that just that, but I am taking a DBA centric approach, and all I want to know is, how do I consume this fast storage in my database?
Yesterday we saw the latest decision in the long-running legal spectacle of Oracle suing Google for allegedly infringing Oracle’s Java API.
Google defeats Oracle in Java code copyright case
I am not a lawyer, nor do I claim any depth of legal expertise. And as engineers, its easy to dismiss these events as one tech giant looking to squeeze some money from another tech giant using their lawyers instead of their products.
But as engineers, these courtroom events should directly concern us.
Increasingly the old paradigm of nightly backing up your large Oracle database to tape, or writing the backup to a NAS share which is then mysteriously swept to tape by some unseen force (the Sys Admins), is becoming an unsustainable approach when backup windows are shrinking, 24/7 availability is becoming the norm and databases are getting larger and larger.
Backup Appliances, such as Sun’s ZDLRA or EMC’s Data Domain, offer many performance and manageability advantages over traditional approaches, and much of the work of traditional backup software is now baked into the appliance itself.
A modern database backup and recovery appliance should include features such as data encryption, compression, de-duplication and remote replication as standard features, to offload those functions from the host CPUs which we want to dedicate to running the database software.
EMC’s Data Domain includes SISL technology – Stream-Informed Segment Layout – to yield some very impressive data reduction numbers using a combination of de-duplication and compression.
But what happens if we choose to use RMAN features in addition to those offered by the backup applicance? What happens if we try to encrypt, de-duplicate, or compress, an RMAN backupset that is itself encrypted or compressed?
During install of Oracle RAC 12c (220.127.116.11), the installer, or possibly the cluster verification utility reports an error:
PRVG-11850 : The system call "connect" failed with error "111" while executing exectask on node ...