Question 1. Installation Of The Demantra Base Application Or Patches?
Create a C:/Tmp folder on the device in which the setup.Exe could be finished prior to the set up as this will generate a log file to this folder
Note that there can also be a few ancillary logs beneath the following folders:
Demand PlannerDatabase ObjectsOracle Server (Oracle back quit database)
Demand PlannerDatabase ObjectsMicrosoft SQL Server (Sql Server lower back cease database)
Question 2. Error Starting The Webserver And/or Deploying The Demantra War File?
Review the Collaborator.Log that's located under the …Collaboratordemantralogs folder at the internet server wherein Demantra is running.
Also, each character webserver (ex. OAS, JRUN, Tomcat, Websphere, and many others…) can have their own person logs in various directories which can also be consulted.
The individual webserver documentation must be reviewed for these log locations.
Oracle 10g Interview Questions
Question 3. Errors With The Demantra Batch Or Simulation Engine?
The key engine logs are observed below the basis drive of the system where the engine is released. The folder that holds those logs normally have Engine2k somewhere inside the call.
Note that there have to be as a minimum Engine2k logs (those are the logs that display the real splitting and forecasts that the engine does) in this folder.
However, to write the grasp EngineManager logs to this folder you need to visit the Engine Administrator (..Demand PlannerAnalytical Enginesbin –> Settings –> Configure) and change the Engine Manager Log tab from STD to FILE.
It is NOT counseled to re-register the engine after making this transformation.
Question 4. Issues With Ebs Integration To Demantra?
In wellknown, most EBS facet activities (ex. Planning Data Pull) may be logged the use of Note 245974.1 however, the Shipment and Bookings Collection job can have more logging turned on with the aid of converting MSD_DEM: Debug Mode to Yes (default is No).
Note that as the Shipment and Bookings Collection process movements to the other aspect of the wall from EBS aspect of the database to the Demantra side of the database (typically indicated by using whilst you start seeing references to the Demantra schema or tables like t_src_items_tmpl or t_src_sales_tmpl_err) then the mistakes might also need to be tracked the use of the Workflow or Active_Proc_Dyn troubleshooting sections of this word.
Oracle 10g Tutorial
Question 5. Stored Procedure Errors With Active_proc_dyn Somewhere In The Error Message?
To view the errors visit Business Modeler –> Tools –> Procedure Error Log
Note that this seems to the backend desk called db_exception_log
Oracle 9i Interview Questions
Question 6. Oracle Demantra Customer, Are You Considering An Upgrade To You Oracle Demantra Software?
There are three vital MOS notes that you may want to study:
12.2.1, 12.2.2, 12.2.Three and 12.2.4 Install Upgrade ADVISOR: Demantra (Doc ID 1664177.2)
DEMANTRA WARNING Have you OR are you Planning to Upgrade to Release 12.2.2? Upgrade from 12.2.2 to twelve.2.3 or 12.2.Four Collections EP Load is Failing ORA-20002, ORA-00001, ORA-06512 (Doc ID 1917715.1)
Upgrading to Demantra 12.2.4? Here are current recognized issues from Demantra Development, Proactive Services and Oracle Support (Doc ID 1928367.1)
Question 7. Upgrading To 12.2.2? Do You Want Extra Speed? Use A Logon Trigger For Parallelism?
When upgrading your Demantra utility from an older version directly to twelve.2.2, you could minimize the improve time. You can force parallelism using a Logon cause at the server.
Creation of recent Indexes on income statistics can take long term.
As part of the upgrade there is a script constructing a new set of indexes, one in keeping with engine profile, on each profile quantity_form expression.
The introduction of the index can take a long time on massive statistics tables.
Remember to disable or drop that trigger whilst the improve has finished.
The following trigger turned into created as SYS database user and tested effectively by using developing DEMANTRA database person and logging in with it:
CREATE OR REPLACE TRIGGER force_parallel_ddl_trg
AFTER LOGON ON database
IF (USER=’DEMANTRA’) THEN
EXECUTE IMMEDIATE ‘ALTER SESSION FORCE PARALLEL DDL’;
Make sure to:
Modify DEMANTRA to be the database schema name.
Drop it after it isn't always wanted anymore the use of the following:
DROP TRIGGER force_parallel_ddl_trg;
Oracle 9i Tutorial Oracle 8i Interview Questions
Question 8. What Happens If Rvwr Cannot Write To Disk?
It relies upon on the context where the write errors occurs:
If there’s a Guaranteed Restore Point, the database crashes to make certain the repair factor assure is not voided.
If there isn’t a Guaranteed Restore Point and it’s a number one database, the Flashback Mode might be robotically turned off for the database, to be able to persevered to function commonly.
If there isn’t a Guaranteed Restore Point and it’s a standby database, the database will hang until the motive of the write failure is fixed.
Question 9. Is It Possible To Specify The Size Of The Flashback Buffer In The Sga?
Yes, but not directly. The size of the Flashback Buffer is about to two * LOG_BUFFER.
For overall performance motives, it’s endorsed to set LOG_BUFFER to as a minimum 8MB for
databases running in Flashback Mode.
UPDATE: For huge 18.104.22.168+ databases with more than a 4GB SGA, you could keep in mind setting LOG_BUFFER to values within the range of 32-64 MB.
Informatica Interview Questions
Question 10. Can Rman Be Used To Backup Flashback Logs?
No. Flashback Logs are not sponsored up. Even if the command BACKUP RECOVERY AREA is used to backup the contents of the FRA to tape simplest the following file sorts are sponsored up: complete and incremental backup sets, manage file autobackups, datafile copies, and archived redo logs.
Flashback Logs are taken into consideration to be transient documents and cannot be sponsored up by means of RMAN. They aren't wanted for media restoration.
Oracle 8i Tutorial
Question eleven. When Are The Flashback Logs Deleted?
Flashback logs are controlled by Oracle handiest. Oracle will try to hold as a whole lot Flashback logs as had to satisfy the DB_FLASHBACK_RETENTION_TARGET parameter. However, if there’s space strain in the Flash Recovery Area (FRA), flashback logs can be deleted to make room for other matters, like backups and archived logs, as an example.
If the fast recovery location has sufficient area, then a flashback log is created every time vital to fulfill the flashback retention goal.
If a flashback log is old sufficient that it's miles not had to fulfill the flashback retention goal, then a flashback log is reused.
If the database need to create a new flashback log and the short healing region is full or there's no disk area, then the oldest flashback log is reused as a substitute.
If the fast recuperation place is complete, then an archived redo log this is reclaimable in keeping with the FRA regulations can be routinely deleted by using the short healing place to make space for different documents. In this situation, any flashback logs that might require the use of that redo log report for using FLASHBACK DATABASE also are deleted.
No file in the rapid healing area is eligible for deletion if it's far required to meet a assured restore point. Thus, retention of flashback logs and different files required to meet the assured restore point, similarly to files required to meet the backup retention policy, can purpose the short healing region to fill absolutely.
PL/SQL Interview Questions
Question 12. How To List Restore Points In Rman?
In RMAN you can use the LIST RESTORE POINT [ALLyou operate a recuperation catalog you can use the view RC_RESTORE_POINT inside the restoration catalog repository, or the command the V$RESTORE_POINT within the goal database.
Oracle 10g Interview Questions
Question thirteen. After Flashback’ing To A Point-in-time Before A Resetlogs Operation Is It Possible To Flash Forward To The Incarnation After The Resetlogs?
Yes, it’s flawlessly possible.
Question 14. Can You See The Progress Of A Flashback Database Operation?
Yes, you can. During a FLASHBACK DATABASE operation you may question V$SESSION_LONGOPS from any other session to peer the development of the flashback.
The FLASHBACK DATABASE operation has awesome stages: the real flashback and the media healing that happens afterwards to bring the database to a consistent nation.
While the actual flashback is walking you’ll see the following message in V$SESSION_LONGOPS, on Oracle 11gR2:
Flashback Database: Flashback Data Applied : 238 out of 282 Megabytes finished
During the media restoration, the subsequent messages can be seen:
Media Recovery: Redo Applied : 263 out of 0 Megabytes finished
Media Recovery: Average Apply Rate : 1164 out of 0 KB/sec done
Media Recovery: Last Applied Redo : 626540 out of 0 SCN+Time achieved
Media Recovery: Elapsed Time : 232 out of 0 Seconds accomplished
Media Recovery: Active Time : 116 out of 0 Seconds accomplished
Media Recovery: Active Apply Rate : 1859 out of zero KB/sec done
Media Recovery: Maximum Apply Rate : 1859 out of 0 KB/sec performed
Media Recovery: Log Files : 15 out of zero Files completed
Media Recovery: Apply Time in line with Log : 7 out of zero Seconds executed
Question 15. How Should I Set The Database To Improve Flashback Performance?
Oracle’s hints are:
Use a quick record device to your flash healing region, ideally with out working device file caching. It is recommended to apply a report gadget that avoids working gadget document caching, inclusive of ASM.
Configure enough disk spindles for the record machine with the intention to preserve the flash recuperation region. For huge manufacturing databases, more than one disk spindles may be needed to support the desired disk throughput for the database to write the flashback logs efficiently.
If the storage system used to preserve the flash restoration area does not have non-risky RAM, try to configure the report machine on pinnacle of striped garage volumes, with a tremendously small stripe length which includes 128K. This will permit each write to the flashback logs to be unfold throughout a couple of spindles, enhancing performance
For huge, production databases, set the init.Ora parameter LOG_BUFFER to be at the least 8MB. This makes sure the database allocates most reminiscence (commonly 16MB) for writing flashback database logs.
Oracle 11g Interview Questions