New answers tagged oracle-11g
It turns out there's a parameter called cursor_sharing that was set to FORCE instead of EXACT select nvl(1,0.0) from DUAL; The query above returns the following depending on the value of the parameter: FORCE=NVL(1,0) EXACT=NVL(1,0.0)
Not that unusual for a best practice if done well. I see read only service accounts and more powerful accounts for web services to connect with create a user and give the user a complex password do not ever create any objects in this schema create a role with connect privilege and which has the appropriate grants on the OBR schema grant the role to the ...
Your only solution for this problem is to take a backup of the datafiles that are hit by a direct load operation, or prevent force_logging operations totally. Force_logging operations may seem like a good idea, performance wise but if you care about your data ..... don't do it. alter database noforce logging;
Top 50 recent answers are included