I want to use oracle cloud autonomous database but not able to see time in IST Timezone.
Is there any way to change timezone from UTC to IST at system level in oracle autonomous database in oracle cloud?
Or any workaround available for autonomous database for apex instance.
Thanks,
Yagnik
You can use the "alter database set time_zone" command and restart the database to change the timezone. Note that if you are using sysdate and systimestamp, those will still return in UTC. You can use the sysdate_at_dbtimezone parameter to make them return in the database timezone you set.
See this doc, https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/autonomous-initialization-parameters.html#GUID-1D5E830F-2986-4E6C-AF8F-899AC3C85D07, for further information.
Related
We are migrating our database from SQL Server to Oracle using the SQL developer tool. While migration, the schema name in SQL Server is "schmdw". This schema is used in our datawarehouse or OLAP database AdvworksDW. After migration we were expecting the schema/user name in oracle will be schmdw. But it is coming as schmdw_AdvworksDW i.e. schemaname_databasename. How can we get rid of this and get the schema/user name in Oracle as schmdw only? Can anyone help me in this regard?
In Oracle, there's no supported way to rename a schema/user. The best solution for you is to create another user, SCHMDW in your case, and give it grants on all objects of the SCHMDW_ADVWORKSDW plus synonyms. Have a look at the second comment on this post, it gives a pl/sql script to automate that.
I need to consume streaming data from an oracle database.
The database team informed me, that the streaming functions are enabled, but how can I make sure of that?
Database version: 19.0.0.0.0
Streams are desupported in Oracle 19c meaning that they can not be used at all. See Oracle Support Doc 2388741.1. It is also mentioned in the release notes for 19c.
We have a 2 current Oracle 10G(10.2.0.1) production databases, and we are planning to migrate to a new database server with Oracle 12C. Since data is for each database is only around 5GB, the best way to create a new instance and use data pump to transfer data. To achieve this, I created a database link from the Oracle 12C database to the 10G, and use that to expdp the data from the 12C database. However when I import the exported data I have around tables that have an error like this:
ORA-39083: Object type TABLE:"USER"."WH_SEARCH_ACT" failed to create with error:
ORA-00406: COMPATIBLE parameter needs to be 12.2.0.0.0 or greater
ORA-00722: Feature "Partition Read Only"
Is there any solution to this other than adding the COMPATIBLE parameter in the production database? This is production so I can't really just update/modify the current production database. Any other solutions here, because i don't like just create the tables before importing the data pump file.
Use the version parameter in the data pump utility. For example:
expdp hr/hr TABLES=hr.employees VERSION=10.2
DIRECTORY=data_pump_dir DUMPFILE=emp10g.dmp LOGFILE=emp.log
Just make sure the version of the export utility is 10g and import utility is 12G. Hope this helps.
In the production database . you can use exp program
exp username/password buffer=64000 file=/path/to/path.dmp full=y
copy exp dump file to oracle 12c and use
imp username/password buffer=64000 file=/path/to/path.dmp full=y
How can I ROLLBACK my database to specific date or point without create a ROLLBACK point?
If you are using Flashback technology you can do it OR using old backup,
Else you couldn't rollback.
Is there a way to restore an Oracle 11g instance from raw data files only? What is the minimum amount of information needed to reconstruct the config files?
Assuming you've shutdown the database cleanly (ie not a SHUTDOWN ABORT), you need to backup...
The Datafiles:
select name from v$datafile
The Database Control Files:
select name from v$controlfile
The Online Redo Logs:
select member from v$logfile
You'll also want to backup your init.ora or spfile
Reference: http://www.adp-gmbh.ch/ora/admin/backup_recovery/cold_backup.html