Search results for query: *

Thank you, T. Your concerns were perfectly valid; one should not abuse the usage of SYSDBA role. That being said, our DBA admitted Flashback feature has been enabled on this server while the other Oracle 11g servers had out of the box configurations. He and I are going to find out whether if...

Hello, T, I was using SYSTEM user when updating through SYNONYM. Yes, there were a role granted to modify this table and another role granted to select from this table, but user SYSTEM who has DBA role should be able to do anything on this table. The fact that same SYSTEM user can update and...

Yes, there was a commit. That's why I was so confused. It only failed to propagate the change from SYNONYM to the physical table on this one particular Oracle 11.1.0.7 Server on Solaris 10. Originally our DBA said Oracle has changed SYNONYM and roles in Oracle 11g, but I proved everything...

Hi!! I may have a server configuration issue here since it only happened to one of our Oracle 11.1.0.7 Servers but not the other Servers at the exact same level. We use PUBLIC SYNONYM to update table data. On this particular Oracle 11.1.0.7 Server, the UPDATE operation was successful and we...

Hi! Khalid, I'm afraid changing MTU parameter will not help. I just found out that all Unix OS source code contains syslogd.h which defines LINEMAX to be 1024 characters; that is, each line in syslog (messages) has a maximum line limit of 1024 characters. Nancy

Hi! When we logged error messages to syslog utility, we found our 3K message got truncated to less than 1K in AIX's messages files. AIX is 5.3 at TL-07. I could not find any document online about the line limit or message limit in the AIX messages files. Is there a configuration parameter...

The User that I used for testing has DBA role granted, and I checked specifically that DBA role on this Oracle instance still had DROP PUBLIC SYNONYM privilege. This is what I have tried: Grant DROP PUBLIC SYNONYM and DROP ANY SYNONYM system privileges to this user, then execute the procedure...

I have a stored procedure that accepts object type and object name as inputs then generates a DROP statement and exec immediate as dynamic SQL. It works fine for all object types except PUBLIC SYNONYM. When user with DBA role (such as "SYSTEM")invokes this procedure to drop a PUBLIC SYNONYM foo...

Thank you! Wished I had read Graeme Birchall's DB2 SQL Cookbook before I had started this venture! Thank you for this excellent pointer! Regards, Nancy

I used to have a dynamic query within a SQL Procedure that used three levels of nested table expression: SELECT C.col1, C.col2 FROM ( SELECT B.col1, B.col2 FROM ( SELECT A.col1, A.col2 FROM ( SELECT ... FROM xxx ORDER BY... ) A ORDER BY... ) B ORDER BY... ) C...