Skip to main content

Posts

migrate obiee rpd

http://www.obieefans.com/create-environment-patch-environmentalization/ Create Environment Patch (Environmentalization) Posted by root on 27 March, 2012No comments yetThis item was filled under [ OBIEE MISC ] During RPD migrations we constantly need to change metadata for the target environment such as physical connection pool(s) and LDAP source(s). To do this manually is time consuming and open for error. Thus, there needs to be a way to script or automate this process. This document will address the automated solution using what is termed in OBI as the patching process. The first migration from Dev->Test, Dev->Prod, or source->target will need to be done manually. Meaning, the RPD that is ready to be migrated to the target environment will need to have its physical connections and LDAP source(s) manually changed for that target environment. That would be done using the BI Admin Tool in offline mode. After which, we can test our changes to ensure that the connections and...

reporting services 2008 and IIS

http://blogs.devhorizon.com/reza/2008/10/20/say-goodbye-to-iis-say-hello-to-httpsys/ Say Goodbye to IIS, Say Hello to HTTP.SYS! With all the issues IIS caused in the previous versions of SSRS, specially to configure it to interact with other applications (such as SharePoint) hosted in IIS , in SSRS 2008, Microsoft made a major architectural shift to move toward to a *real* Single Service Architecture that would eliminate dependency on IIS. You no longer require having IIS installed on the RS box and, even nicer; you don’t have to install SQL on that RS box! Well, let me rephrase what I just said above. SSRS doesn’t require IIS to function, but this only applies when you configure it in native mode. In integrated mode and since you have to join the SSRS machine to the farm, you have to install SharePoint WFE components on RS machine and this means dependency on IIS, but again that’s the dependency SharePoint has on IIS , not SSRS! This shifting architectural decision took care of two ve...

DBA_HIST_SYSMETRIC_SUMMARY

To generate oracle workload metrics report, use the following query to generate date sqlplus> col metric_name format a39 select metric_name,substr(to_char(begin_interval_time,'hh24:mi'),1,4)||'0' snapshot, sum(case to_char(begin_interval_time,'yyyymmdd') when '20120208' then round(average) end) as date20120208, sum(case to_char(begin_interval_time,'yyyymmdd') when '20120209' then round(average) end) as date20120209, sum(case to_char(begin_interval_time,'yyyymmdd') when '20120210' then round(average) end) as date20120210 from DBA_HIST_SYSMETRIC_SUMMARY,dba_hist_snapshot where dba_hist_snapshot.snap_id=DBA_HIST_SYSMETRIC_SUMMARY.snap_id and metric_name in ('Physical Reads Per Sec','Physical Writes Per Sec','Redo Generated Per Sec','Logical Reads Per Sec','Host CPU Utilization (%)','Current Logons Count','Executions Per Sec') and to_char(begin_interval_time,'yyyym...

oracle autotrace

http://www.dba-oracle.com/t_OracleAutotrace.htm Oracle autotrace supports the following options: • autotrace on – Enables all options. • autotrace on explain – Displays returned rows and the explain plan. • autotrace on statistics – Displays returned rows and statistics. • autotrace trace explain – Displays the execution plan for a select statement without actually executing it. "set autotrace trace explain" • autotrace traceonly – Displays execution plan and statistics without displaying the returned rows. This option should be used when a large result set is expected.

sqlserver drop user error

If you try to drop a user that owns a schema, you will receive the following error message: The database principal owns a schema in the database, and cannot be dropped. In order to drop the user, you need to find the schemas they are assigned, then transfer the ownership to another user or role SELECT s.name FROM sys.schemas s WHERE s.principal_id = USER_ID('hydepark') -- now use the names you find from the above query below in place of the SchemaName below ALTER AUTHORIZATION ON SCHEMA::SchemaName TO dbo

export ORA_RMAN_SGA_TARGET

ORA-4031 During Startup Nomount using RMAN without parameter file (PFILE) [ID 1176443.1] -------------------------------------------------------------------------------- Modified 06-DEC-2010 Type PROBLEM Status PUBLISHED In this Document Symptoms Cause Solution -------------------------------------------------------------------------------- Applies to: Oracle Server - Enterprise Edition - Version: 11.2.0.1 and later [Release: 11.2 and later ] Information in this document applies to any platform. Symptoms RMAN startup nomount failed with ORA-4031 Customer was testing RMAN backup/restore in Exadata. Customer firstly backup the database to tape and then remove all the datafiles, spfile, controlfiles for testing. Then during the recover, customer connected RMAN with nocatalog and try to "startup nomount", then ORA-4031 occured. ==================== Log ======================== oracle@hkfop011db01:/home/oracle $ export ORACLE_SID=TEST oracle@test011db01:/home/...