317 reputation
16
bio website justwidgets.com
location Connecticut
age
visits member for 2 years, 9 months
seen Jul 3 at 10:22

Oracle user since 1999 but still have a lot to learn. Also learning and doing a bit of Microsoft SQL Server and Java programming too, among other things...


Apr
14
awarded  Yearling
Nov
17
awarded  Commentator
Nov
17
comment As a DBA, how would I go about transitioning from Oracle to SQL Server?
Oracle also allows mixing char/varchar2 and nchar/nvarchar2 types with two different encodings - see Unicode characters can be stored in an Oracle database in two ways.
Oct
30
comment How to set an Oracle user's default schema?
Great idea but since when others then null; is a catch-all, it will complicate troubleshooting since it makes any error invisible. Maybe remove the exception handling entirely or log the error on the server in an AUTONOMOUS transaction and then re-RAISE it?
Sep
18
comment How to install Oracle 10g Express and 11g Enterprise on same machine
Could a regularly scheduled job using JDBC take data from staging table(s) on 11g and insert/update 8i instead?
Sep
14
revised Resolving ORA-01033 “initialization or shutdown in progress”
Small but significant typo in the title for the key command: "expdp" was "exdp"
Sep
13
suggested suggested edit on Resolving ORA-01033 “initialization or shutdown in progress”
Sep
11
revised Resolving ORA-01033 “initialization or shutdown in progress”
expdb is not for physical "backups" http://orafaq.com/node/2392 The word "backup" is not on the page cited by the asker.
Sep
11
suggested suggested edit on Resolving ORA-01033 “initialization or shutdown in progress”
Sep
9
comment Comparing date and timestamp variables in a where clause in a procedure
I'm not really sure. If the SQL execution plans of both scenarios are the same or performance is comparable, not using the intermediate variables should be OK. It just surprised me that incrementing to the next day with a simple "+ 1" would cause the PLW-07204 warning. But I guess since "1" is of course not a TIMESTAMP type, implict type conversion is going on at some level, like how these return different types: select DUMP(CURRENT_TIMESTAMP), DUMP(CURRENT_TIMESTAMP + 1) from dual.
Sep
9
awarded  Autobiographer
Sep
9
revised Comparing date and timestamp variables in a where clause in a procedure
Edit to please the compiler
Sep
9
revised Comparing date and timestamp variables in a where clause in a procedure
added 263 characters in body - more exact link
Sep
9
answered Comparing date and timestamp variables in a where clause in a procedure
Sep
9
comment Comparing date and timestamp variables in a where clause in a procedure
To prevent the PLW-07204 warning, convert myDatabaseTimeStamp before using it in the SQL statement: 1. Before the BEGIN section create: myDatabase DATE; 2. Right before the SQL do: myDatabase := cast(myDatabaseTimeStamp as DATE); 3. TRUNC() is only defaulting the time to midnight. Even though "inputDate" is a DATE type it could contain time.
Sep
9
comment Comparing date and timestamp variables in a where clause in a procedure
What if "inputDate" also includes time? - so both sides have to use trunc()? Or if there's an index on "inputDate" BETWEEN or >= and < should be used. Try this in SQLFiddle: SELECT * FROM test WHERE trunc(col) = trunc(CURRENT_TIMESTAMP);
Jul
3
comment Mismatched Oracle drivers - need upgrade (10.2.0.1 to 10.2.0.5)
The 10.2.0.X clients can be patched but I don't think they can be upgraded from say 10.2.0.4 to 10.2.0.5. Also multiple clients can be installed side-by-side. On WinXP, I've had 8.1.6 and 10.2.0.4 ODBC drivers installed on a single PC. Have you considered installing the Instant client + ODBC supplement? It takes up less disk space than the full Oracle client.
Jun
30
answered Oracle subquery column aliasing syntax?
Jun
29
comment Mismatched Oracle drivers - need upgrade (10.2.0.1 to 10.2.0.5)
It's not clear from your post here that the "drivers" are Oracle ODP.NET (not ODBC, JDBC, etc.). Only the forums.oracle.com link mentions .NET in the ODP.NET forum.
Jun
10
comment Simple date calculation to show specified old records
More recent dates are greater than older dates so if you only want logins less than 48 hours and 0 seconds old, it should be WHERE logon_time + 2 > SYSDATE. As for, using '8-JUN-12' it's safer to explicitly convert that string to a date with something like: TO_CHAR('08-JUN-2012', 'DD-MON-YYYY').