PeopleTools update before or after database creation

Hi, there:
We need to create a new environment with latest PeopleTools and FSCM. The latest PeopleTools is 8.49.20. Can I install PT 8.49.20 before creating the database? Or I need to create the datbase first and then update the PeopleTools.
Thanks for any help.

The latest Peopletools version/patches is 8.49.21 :-)
And, yes, you can install the latest PT before creating the database.
Just be aware, all the Peoplesoft application 9 (I assume you want FSCM9.0) have been delivered within Peopltools 8.48, that means you'll have to upgrade your database to the latest version of the Peopletools (the one you are installing) immediately after the database creation/load. Follow the dedicated chapter in the Peopletools install guide.
Nicolas.

Similar Messages

Should I download Aperture 3.6 compatibility update before or after downloading Yosemite?

I'm running Mavericks OS on my late 2009 MacBook.
I would like to download Yosemite but I'm worried about my photos on Aperture 3. Should I download the Aperture 3.6 compatibility update before or after downloading Yosemite.? Thanks.

I bought Aperture 3 from the App Store some time ago but got it updated regularly
Does that mean, you are now running Aperture 3.5.1? Then you should be seeing Aperture on the Purchases tab of the App Store and your Aperture license has been associated with your Apple ID.

Do i install apples 10.5.8 updates before or after i install 10.6?

Im upgrading from leopard to snow leop., but i just noticed there are several software updates and hardware updates available from apple that i need, should i d
o them before or after i install snow l.?

You don't need any updates for Leopard. See the following:
Snow Leopard General requirements
Mac computer with an Intel processor
1GB of memory
5GB of available disk space
DVD drive for installation
Some features require a compatible Internet service provider; fees may apply.
Some features require Apple’s MobileMe service; fees and terms apply.
Now, if you wish to access the App Store you will need to update Snow Leopard to 10.6.6 or greater. To do that after you've installed Snow Leopard just download and install Mac OS X 10.6.8 Update Combo v1.1.

Creation parameters not taking effect after database creation in 10.1.0.4

I created a database using DBCA, changed the default nls settings, then finished the database creation.
The alert log reports the parameters as different than the defaults
However, when starting the instance, the nls parameters are only set at the instance level and not the database level.
Has anyone seen something similar in 10.1.0.4?
Thanks

Found this in Oracle Doc,
NLS_DATABASE_PARAMETERS is the one you set when you do Create Database.
NLS_INSTANCE_PARAMETERS is the one you set in your spfile when you start instance.
So if you didn't set NLS_INSTANCE_PARAMETERS in spfile, then instance will start with NLS_DATABASE_PARAMETERS
And alter session will over write them all.
It's not new behavior in 10.2.0.4
==============================================
NLS Database Parameters
When a new database is created during the execution of the CREATE DATABASE statement, the NLS-related database configuration is established. The current NLS instance parameters are stored in the data dictionary along with the database and national character sets. The NLS instance parameters are read from the initialization parameter file at instance startup.
You can find the values for NLS parameters by using:
NLS Data Dictionary Views
NLS Dynamic Performance Views
OCINlsGetInfo() Function
NLS Data Dictionary Views
Applications can check the session, instance, and database NLS parameters by querying the following data dictionary views:
NLS_SESSION_PARAMETERS shows the NLS parameters and their values for the session that is querying the view. It does not show information about the character set.
NLS_INSTANCE_PARAMETERS shows the current NLS instance parameters that have been explicitly set and the values of the NLS instance parameters.
NLS_DATABASE_PARAMETERS shows the values of the NLS parameters for the database. The values are stored in the database.

Delete cube request - before or after index creation?

Hi Folks,
a quick question. I plan to delete for one cube requests that are older than 3 days (cube only hosts short term reporting). Now I wonder if this should be done aftter the new load but before the index is created or after the index is created.
I guess it is after the index is created otherwise it would take longer to find the requests that should be deleted. The index will be slighly degenerated due to the deletion but should be only marginal.
I am right or wrong?
Thanks for all replies in advance,
Axel

hi,
a quick question. I plan to delete for one cube requests that are older than 3 days (cube only hosts short term reporting). Now I wonder if this should be done aftter the new load but before the index is created or after the index is created.
The delete should be done before index creation, as once the index are created then even though the data corresponding to those index is deleted the index still remains. This unnecessarily increases the index table size
regards,
Arvind.

SQLplus doesn't allow login after database creation login

I can login in to SQLplus right after the DB config assist completes but after I close out of SQLplus I cannot login again.
I get the error messeages:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist.

Benjamin,
Assuming that your OS is Windows, try this --
Open Services in Control Panel
Select TNSListener
Open properties
On the 'Log On' tab, put your operating system login name and password.
Save the changes.
Do the same for Oracleservice.
Restart the services or computer
Let me know how this goes

Update apps before or after upgrade?

I've got numerous updates waiting. So should I update before or after I upgrade to IO5? Your thoughts?

OK, I'l answer/update my question. Yesterday, I backed up my iPad 2 and then downloaded/installed the new IO5 (as per directions via iTunes). That took most of the morning. Then I updated my apps. Most seem to work fine. However, one app (FreeBooks) quit/exited every time I tried to use it, and my library was gone. So I just ended up deleting the app. Then I reinstalled it and re-downloaded my library. Bit of a pain but no big deal. So my upgrade went pretty well. I'm loving the new four-finger gestures so I don't have to use the Home button as much.

Physical Standby Database Creation with RMAN

Hi,
I'm in 10g on Linux. I want to create a standby database on another Linux server. I did not find a clear procedure to create it in Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02
and niether in Oracle® Data Guard Concepts and Administration 10g Release 2 (10.2) B14239-04
In the last one chapter 3 sends you to F appendix and F appendix says do nothing before having than all in chapter 3 :
In F.1.1 page F-2 it is said :
See Chapter 3 for a complete discussion of physical standby database preparation,including initialization parameter settings. You must perform all necessary preparation tasks described in these chapters before RMAN can successfully create the standby database files and mount the standby database.
Any way I'm looking for a procedure or clear article to create it.
Many thanks before.

Physical Standby Database Creation with RMAN
Use the DUPLICATE command.
Check out this metalink doc: Note:374069.1 and Note:118409.1
Message was edited by:
STW
Message was edited by:
STW

Updates on a specific COLUMN is not generating a BEFORE or AFTER value ...

I have a table SCHEMA_OWNER.RX_TX table that has 182 columns. Here is the extract param file. Also on this table i have enabled ALL COLUMNS to be supplimental logged via "alter table SCHEMA_OWNER.RX_TX add supplemental log data (all) columns". The table has a PK on the "ID" column. Please note that the POS_REFUND_DATE column in the table SCHEMA_OWNER.RX_TX is 178th column.
When i execute the following UPDATE followed by a COMMIT, when the current value of POS_REFUND_DATE=NULL, i do not see TRAIL records getting created in the trail file.
SQL>Update Eps2_Kp_900001058.Rx_Tx Set Pos_Refund_Date=Pos_Refund_Date Where Tx_Number=1014524 And Nhin_Store_Id=900001058 And Id=4575035;
SQL>COMMIT;
NOTE: If POS_REFUND_DATE is NOT NULL, before the above UPDATE is executed, then TRAIL RECORDS (i.e. before and after trail records) are successfully created.
Here is param file for the EXTRACT=EXTPROD
EXTRACT EXTPROD
SETENV (ORACLE_SID = "opepsd2")
SETENV (ORACLE_HOME = "/u01/app/oradev/product/11.2.0.3/db_1")
SETENV (NLS_LANG="AMERICAN_AMERICA.WE8MSWIN1252")
USERID ogguser, PASSWORD AACAAAAAAAAAAAKAJISJVHPCJAEJKJIHWHVCXHQIWIZEUCJF, ENCRYPTKEY DEFAULT
EXTTRAIL /u02/ggoppr/trail/SP
TRANLOGOPTIONS DBLOGREADER
CACHEMGR CACHEBUFFERSIZE 64KB, CACHESIZE 2GB, CACHEDIRECTORY ./dirtmp
GETUPDATEBEFORES
NOCOMPRESSDELETES
NOCOMPRESSUPDATES
STATOPTIONS RESETREPORTSTATS
REPORT AT 00:01
REPORTROLLOVER AT 00:01
REPORTCOUNT EVERY 60 SECONDS, RATE
WARNLONGTRANS 2 HOURS
TABLE EPS2_KP_900001058.RX_TX , COLS (ID,NHIN_STORE_ID,POS_SOLD_DATE,LAST_DML_BY_CONVERSION_DATE,RETURNED_DATE,POS_REFUND_DATE,UNSELL_DATE,ADMIN_REBILLED_DATE,PARTIAL_FILL_STATUS) , TOKENS ( NHIN_STORE_ID = "900001058" );
Here are some usefull output from GGSCI:
GGSCI (szabdb32) 4> dblogin userid ogguser , password ogguser123
Successfully logged into database.
GGSCI (szabdb32) 5> info all
Program Status Group Lag Time Since Chkpt
MANAGER RUNNING
EXTRACT RUNNING EXTDEV2 00:00:00 00:00:07
Description EPS Extract
EXTRACT RUNNING EXTPROD 00:00:00 00:00:04
EXTRACT RUNNING EXTSALE 00:00:00 00:00:04
EXTRACT RUNNING EXTTEST 00:00:00 00:00:04
EXTRACT RUNNING PMPDEV2 00:00:00 00:00:02
EXTRACT RUNNING PMPPROD 00:00:00 00:00:01
EXTRACT RUNNING PMPSALE 00:00:00 00:00:05
EXTRACT RUNNING PMPTEST 00:00:00 00:00:05
EXTRACT RUNNING RPMPDEV2 00:00:00 00:00:06
Here is the DDL structure of the table object "EPS2_KP_900001058.RX_TX" (vERY LONg)
CREATE TABLE "EPS2_KP_900001058"."RX_TX"
( "ID" NUMBER(38,0) NOT NULL ENABLE,
"NHIN_STORE_ID" NUMBER(10,0) NOT NULL ENABLE,
"DELETED" VARCHAR2(1 BYTE),
"BRAND_ACQUISITION_COST" NUMBER(13,2),
"AUTO_COUNTING_SYSTEM_PRIORITY" VARCHAR2(1 BYTE),
"CHARGE" VARCHAR2(1 BYTE),
"COMPOUND_FEE" NUMBER(13,2),
"BASE_COST" NUMBER(13,2),
"COUNSELING_CHOICE" VARCHAR2(1 BYTE),
"NCPDP_DAW" VARCHAR2(1 BYTE),
"FILL_QUANTITY" NUMBER(13,4),
"BRAND_DISCOUNT" NUMBER(13,2),
"DRUG_EXPIRATION_DATE" DATE,
"FILL_DATE" DATE,
"PICKED_UP" VARCHAR2(1 BYTE),
"HOST_RETRIEVAL_DATE" DATE,
"MANUFACTURER" VARCHAR2(10 BYTE),
"SAFETY_CAP_FLAG" VARCHAR2(1 BYTE),
"PAC_MED" VARCHAR2(1 BYTE),
"REFILL_NUMBER" NUMBER(5,0),
"REPORTABLE_SALES_DATE" DATE,
"FILL_STATUS" VARCHAR2(1 BYTE),
"TAX_AMOUNT" NUMBER(13,2),
"TP_BILL" VARCHAR2(1 BYTE),
"UC_PRICE" NUMBER(13,2),
"UP_CHARGE" NUMBER(13,2),
"USUAL" VARCHAR2(1 BYTE),
"DAYS_SUPPLY" NUMBER(10,0),
"DRUG_SCHEDULE" VARCHAR2(1 BYTE),
"DAYS_SUPPLY_BASIS" VARCHAR2(1 BYTE),
"FOLLOW_UP_DATE" DATE,
"GROUP_ON_RX" VARCHAR2(3 BYTE),
"ICD9" VARCHAR2(7 BYTE),
"ICD9_TYPE" VARCHAR2(1 BYTE),
"NUM_LABELS" NUMBER(3,0),
"OWED" NUMBER(13,4),
"PRESCRIBED_QUANTITY" NUMBER(13,4),
"STOP_DATE" DATE,
"WRITTEN_DATE" DATE,
"DISPENSED_DRUG_NDC" VARCHAR2(11 BYTE),
"LANG" VARCHAR2(2 BYTE) NOT NULL ENABLE,
"SIG_PER_DAY" NUMBER(13,4),
"SIG_PER_DOSE" NUMBER(13,4),
"SIG_TEXT" VARCHAR2(515 BYTE),
"REFILL_SOURCE" NUMBER(5,0),
"TX_DELETED" VARCHAR2(1 BYTE),
"TX_NUMBER" NUMBER(12,0),
"CENTRAL_FILL_CUTOFF_DATE" DATE,
"BRAND_PRICE" NUMBER(13,2),
"GENERIC_PRICE" NUMBER(13,2),
"DRUG_DISPENSED" VARCHAR2(1 BYTE),
"POS_STATUS" VARCHAR2(1 BYTE),
"POS_INVOICE_NUMBER" NUMBER(35,0),
"CASHIER_NAME" VARCHAR2(28 BYTE),
"REGISTER_NUM" VARCHAR2(20 BYTE),
"POS_OVERRIDDEN_NET_PAID" NUMBER(13,2),
"POS_REASON_FOR_VOID" VARCHAR2(120 BYTE),
"RX_STOLEN" VARCHAR2(1 BYTE),
"POS_BARCODE_NUM" NUMBER(20,0),
"RETURNED_DATE" DATE,
"RX_CREDIT_INITIATOR" VARCHAR2(1 BYTE),
"ORIGINAL_QTY" NUMBER(13,4),
"ORIGINAL_PRICE" NUMBER(13,2),
"OLD_RX_TX_ID" NUMBER(38,0),
"NEW_RX_TX_ID" NUMBER(38,0),
"PATIENT_DISEASE_ID" NUMBER(38,0),
"PRICE_CODE_ID" NUMBER(38,0),
"TAX_ID" NUMBER(38,0),
"COMPOUND_ID" NUMBER(38,0),
"DRUG_BRAND_ID" NUMBER(38,0),
"DRUG_GENERIC_ID" NUMBER(38,0),
"REFERENCE_BRAND_ID" NUMBER(38,0),
"KEEP_SAME_DRUG" VARCHAR2(1 BYTE),
"DIFFERENT_GENERIC" VARCHAR2(1 BYTE),
"RX_SUMMARY_ID" NUMBER(38,0),
"PRESCRIBER_CLINIC_LINK_ID" NUMBER(38,0),
"SUPV_PRESCRIBER_CLINIC_LINK_ID" NUMBER(38,0),
"DRUG_COST_TYPE_ID" NUMBER(38,0),
"BASECOST_ID" NUMBER(38,0),
"REQUESTED_PRICE_TO_QTY" NUMBER(13,2),
"OVERRIDDEN_PRICE_AMOUNT" NUMBER(13,2),
"PRICE_OVERRIDE_REASON" VARCHAR2(1 BYTE),
"PRICE_OVERRIDE_NOTE_ID" NUMBER(38,0),
"GENERIC_ACQUISITION_COST" NUMBER(13,2),
"GENERIC_DISCOUNT" NUMBER(13,2),
"PROFESSIONAL_FEE" NUMBER(13,2),
"NO_SALES_TAX" VARCHAR2(1 BYTE),
"COMPETITIVE_PRICED" VARCHAR2(1 BYTE),
"USING_PERCENT_OF_BRAND" VARCHAR2(1 BYTE),
"USING_COMPOUND_PLAN_PRICING" VARCHAR2(1 BYTE),
"ALLOW_PRICE_OVERRIDE" VARCHAR2(1 BYTE),
"POS_SOLD_DATE" DATE,
"FILL_LOCATION" VARCHAR2(1 BYTE),
"NOTES" VARCHAR2(2000 BYTE),
"DRUG_IMAGE_KEY" VARCHAR2(255 BYTE),
"BRAND_MANUALLY_SELECTED" VARCHAR2(1 BYTE),
"GENERIC_MANUALLY_SELECTED" VARCHAR2(1 BYTE),
"TX_STATUS" VARCHAR2(1 BYTE),
"RETURNED_USER_ID" NUMBER(38,0),
"DE_INITIALS" VARCHAR2(3 BYTE),
"DV_INITIALS" VARCHAR2(3 BYTE),
"PV_INITIALS" VARCHAR2(3 BYTE),
"OVERRIDE_USER_ID" NUMBER(38,0),
"PARTIAL_FILL_STATUS" VARCHAR2(1 BYTE),
"PARTIAL_FILL_BILLING_TYPE" VARCHAR2(1 BYTE),
"INTENDED_QUANTITY" NUMBER(13,4),
"PATIENT_REQUESTED_PRICE" VARCHAR2(1 BYTE),
"MISSING_DATE" DATE,
"REPLACE_DATE" DATE,
"RETURN_TO_STOCK_DATE" DATE,
"RX_COM_DOWN" VARCHAR2(1 BYTE),
"RPH_NAME_OF_RECORD" VARCHAR2(60 BYTE),
"CUSTOM_SIG" VARCHAR2(1 BYTE),
"DISCOUNT_ID" NUMBER(38,0),
"PATIENT_REQUEST_BRAND_GENERIC" VARCHAR2(1 BYTE),
"WILL_CALL_PICKED_UP_DATE" DATE,
"COMPLETION_RX_TX_ID" NUMBER(38,0),
"PARTIAL_RX_TX_ID" NUMBER(38,0),
"SENT_TO_EHR" VARCHAR2(1 BYTE) DEFAULT 'N',
"DRUG_IMAGE_START_DATE" DATE,
"ADMIN_REBILLED" VARCHAR2(1 BYTE),
"SIG_CODE" VARCHAR2(20 BYTE),
"SIG_TEXT_FOREIGN_LANGUAGE" VARCHAR2(515 BYTE),
"RTRN_PRESCRIBER_CLINIC_LINK_ID" NUMBER(38,0),
"OUTSOURCE_COMPOUND" VARCHAR2(1 BYTE),
"IMPRINT_TEXT" VARCHAR2(512 BYTE),
"IMPRINT_SOURCE" VARCHAR2(36 BYTE),
"DIB_PEM_IDENTIFIER" VARCHAR2(20 BYTE),
"DIB_DATABASE_VERSION" VARCHAR2(5 BYTE),
"DIB_ISSUE_DATE" DATE,
"COST_VERIFIED" VARCHAR2(1 BYTE),
"SEND_TO_PRESCRIBER_WILDCARD" VARCHAR2(1 BYTE),
"COUNSELING_RPH_INITIALS" VARCHAR2(3 BYTE),
"STATE_REPORT_STATUS" VARCHAR2(1 BYTE),
"REQUIRE_RELATION_TO_PATIENT" VARCHAR2(1 BYTE),
"PHOTO_ID_STATE" VARCHAR2(3 BYTE),
"PHOTO_ID_TYPE" VARCHAR2(2 BYTE),
"PHOTO_ID_NUMBER" VARCHAR2(20 BYTE),
"RELATIONSHIP_TO_PATIENT" VARCHAR2(2 BYTE),
"PICKUP_FIRST_NAME" VARCHAR2(50 BYTE),
"PICKUP_LAST_NAME" VARCHAR2(50 BYTE),
"REQUIRE_PICKUP_ID_TYPE" VARCHAR2(1 BYTE),
"REQUIRE_PICKUP_ID_STATE" VARCHAR2(1 BYTE),
"REQUIRE_PICKUP_ID_NAME" VARCHAR2(1 BYTE),
"REQUIRE_PICKUP_ID_NUMBER" VARCHAR2(1 BYTE),
"REQUIRE_PICKUP_ID_EXPIRATION" VARCHAR2(1 BYTE),
"PHOTO_ID_EXPIRE_DATE" DATE,
"PATIENT_DELIVERY_NOTES_ID" NUMBER(38,0),
"CANCEL_REASON" VARCHAR2(2 BYTE),
"COUNSELING_RPH_EMPLOYEE_NUM" VARCHAR2(255 BYTE),
"RPH_COUNSEL_NOTES_ID" NUMBER(38,0),
"MEMBERSHIP_INDICATOR" VARCHAR2(1 BYTE),
"COUNSEL_REASON" VARCHAR2(2 BYTE),
"POS_VOID_REASON_CODE" VARCHAR2(10 BYTE),
"AUTHORIZING_MANAGER_NAME" VARCHAR2(255 BYTE),
"FREQUENCY_RATE" NUMBER(13,4),
"INCREMENTAL_CONV_SENT_TO_EHR" VARCHAR2(1 BYTE),
"ENTERPRISE_RX_FILL_COUNT" NUMBER(5,0),
"INTENDED_DAYS_SUPPLY" NUMBER(10,0),
"DDID_USED_BY_DRUG_SELECTION" NUMBER(10,0),
"GPI_USED_BY_DRUG_SELECTION" VARCHAR2(24 BYTE),
"NEW_DDID_AUTHORIZED_BY_EMP_NUM" VARCHAR2(255 BYTE),
"TIME_FRAME" NUMBER(2,0),
"TIME_FRAME_TYPE" NUMBER(2,0),
"LAST_DML_BY_CONVERSION_DATE" TIMESTAMP (6),
"END_OF_THERAPY_DATE" TIMESTAMP (6),
"UNSELL_DATE" TIMESTAMP (6),
"UNSELL_QUALIFIER" VARCHAR2(2 BYTE),
"ADMIN_REBILLED_DATE" TIMESTAMP (6),
"LAST_UPDATE_DATE" TIMESTAMP (6),
"TP_LAST_UPDATE_DATE" TIMESTAMP (6),
"ADMIN_REBILL_QUALIFIER" VARCHAR2(3 BYTE),
"PRIOR_RETURN_REASON_CODE" VARCHAR2(2 BYTE),
"POS_PRICE_ADJUSTMENT_CODE" VARCHAR2(2 BYTE),
"TX_SOLD_QUALIFIER" VARCHAR2(3 BYTE),
"MEDICARE_NOTICE" VARCHAR2(1 BYTE),
"POS_REFUND_REASON_CODE" VARCHAR2(10 BYTE),
"POS_REASON_FOR_REFUND" VARCHAR2(120 BYTE),
"POS_REFUND_DATE" TIMESTAMP (6),
"MEDGUIDE_TO_PRINT" VARCHAR2(1 BYTE),
"PATIENT_EDUCATION_TO_PRINT" VARCHAR2(1 BYTE),
"EXCLUDED_OTC" VARCHAR2(1 BYTE),
CONSTRAINT "RX_TX_PK" PRIMARY KEY ("ID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ENABLE,
SUPPLEMENTAL LOG DATA (ALL) COLUMNS,
SUPPLEMENTAL LOG GROUP "GGS_RX_TX_78190" ("ID") ALWAYS,
CONSTRAINT "NOTES_FK1" FOREIGN KEY ("RPH_COUNSEL_NOTES_ID")
REFERENCES "EPS2_KP_900001058"."NOTES" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK1" FOREIGN KEY ("PRICE_OVERRIDE_NOTE_ID")
REFERENCES "EPS2_KP_900001058"."NOTES" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK10" FOREIGN KEY ("DISCOUNT_ID")
REFERENCES "EPS2_KP_900001058"."DISCOUNT" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK11" FOREIGN KEY ("SUPV_PRESCRIBER_CLINIC_LINK_ID")
REFERENCES "EPS2_KP_900001058"."PRESCRIBER_CLINIC_LINK" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK12" FOREIGN KEY ("PATIENT_DISEASE_ID")
REFERENCES "EPS2_KP_900001058"."PATIENT_DISEASE" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK13" FOREIGN KEY ("PRESCRIBER_CLINIC_LINK_ID")
REFERENCES "EPS2_KP_900001058"."PRESCRIBER_CLINIC_LINK" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK14" FOREIGN KEY ("RX_SUMMARY_ID")
REFERENCES "EPS2_KP_900001058"."RX_SUMMARY" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK15" FOREIGN KEY ("DRUG_GENERIC_ID")
REFERENCES "EPS2_KP_900001058"."DRUG" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK16" FOREIGN KEY ("DRUG_BRAND_ID")
REFERENCES "EPS2_KP_900001058"."DRUG" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK17" FOREIGN KEY ("COMPOUND_ID")
REFERENCES "EPS2_KP_900001058"."COMPOUND" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK18" FOREIGN KEY ("RETURNED_USER_ID")
REFERENCES "EPS2_KP_900001058"."USERS" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK2" FOREIGN KEY ("TAX_ID")
REFERENCES "EPS2_KP_900001058"."TAX" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK20" FOREIGN KEY ("DRUG_COST_TYPE_ID")
REFERENCES "EPS2_KP_900001058"."DRUG_COST_TYPE" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK21" FOREIGN KEY ("BASECOST_ID")
REFERENCES "EPS2_KP_900001058"."BASECOST" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK22" FOREIGN KEY ("COMPLETION_RX_TX_ID")
REFERENCES "EPS2_KP_900001058"."RX_TX" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK23" FOREIGN KEY ("PARTIAL_RX_TX_ID")
REFERENCES "EPS2_KP_900001058"."RX_TX" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK24" FOREIGN KEY ("RTRN_PRESCRIBER_CLINIC_LINK_ID")
REFERENCES "EPS2_KP_900001058"."PRESCRIBER_CLINIC_LINK" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK25" FOREIGN KEY ("PATIENT_DELIVERY_NOTES_ID")
REFERENCES "EPS2_KP_900001058"."NOTES" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK4" FOREIGN KEY ("PRICE_CODE_ID")
REFERENCES "EPS2_KP_900001058"."PRICE_CODE" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK5" FOREIGN KEY ("REFERENCE_BRAND_ID")
REFERENCES "EPS2_KP_900001058"."DRUG" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK6" FOREIGN KEY ("OLD_RX_TX_ID")
REFERENCES "EPS2_KP_900001058"."RX_TX" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK7" FOREIGN KEY ("NEW_RX_TX_ID")
REFERENCES "EPS2_KP_900001058"."RX_TX" ("ID") ENABLE NOVALIDATE,
CONSTRAINT "RX_TX_FK9" FOREIGN KEY ("OVERRIDE_USER_ID")
REFERENCES "EPS2_KP_900001058"."USERS" ("ID") ENABLE NOVALIDATE
) SEGMENT CREATION IMMEDIATE
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_DATA" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX1" ON "EPS2_KP_900001058"."RX_TX" ("DISCOUNT_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX10" ON "EPS2_KP_900001058"."RX_TX" ("PRICE_OVERRIDE_NOTE_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX11" ON "EPS2_KP_900001058"."RX_TX" ("BASECOST_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX12" ON "EPS2_KP_900001058"."RX_TX" ("REFERENCE_BRAND_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX13" ON "EPS2_KP_900001058"."RX_TX" ("RX_SUMMARY_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX15" ON "EPS2_KP_900001058"."RX_TX" ("SUPV_PRESCRIBER_CLINIC_LINK_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX16" ON "EPS2_KP_900001058"."RX_TX" ("TAX_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX17" ON "EPS2_KP_900001058"."RX_TX" ("TX_NUMBER")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX18" ON "EPS2_KP_900001058"."RX_TX" ("DISPENSED_DRUG_NDC")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX19" ON "EPS2_KP_900001058"."RX_TX" ("DRUG_COST_TYPE_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX2" ON "EPS2_KP_900001058"."RX_TX" ("COMPOUND_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX20" ON "EPS2_KP_900001058"."RX_TX" ("OVERRIDE_USER_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX21" ON "EPS2_KP_900001058"."RX_TX" ("RETURNED_USER_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE UNIQUE INDEX "EPS2_KP_900001058"."RX_TX_IX22" ON "EPS2_KP_900001058"."RX_TX" (CASE "NHIN_STORE_ID" WHEN 900001058 THEN "TX_NUMBER" ELSE NULL END )
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX23" ON "EPS2_KP_900001058"."RX_TX" ("COMPLETION_RX_TX_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX24" ON "EPS2_KP_900001058"."RX_TX" ("PARTIAL_RX_TX_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX28" ON "EPS2_KP_900001058"."RX_TX" (TRUNC("REPORTABLE_SALES_DATE"))
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX29" ON "EPS2_KP_900001058"."RX_TX" ("PATIENT_DELIVERY_NOTES_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX3" ON "EPS2_KP_900001058"."RX_TX" ("DRUG_BRAND_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX30" ON "EPS2_KP_900001058"."RX_TX" ("FILL_LOCATION")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX31" ON "EPS2_KP_900001058"."RX_TX" ("FILL_DATE")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX4" ON "EPS2_KP_900001058"."RX_TX" ("DRUG_GENERIC_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX5" ON "EPS2_KP_900001058"."RX_TX" ("NEW_RX_TX_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX6" ON "EPS2_KP_900001058"."RX_TX" ("OLD_RX_TX_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX7" ON "EPS2_KP_900001058"."RX_TX" ("PATIENT_DISEASE_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX8" ON "EPS2_KP_900001058"."RX_TX" ("PRESCRIBER_CLINIC_LINK_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
CREATE INDEX "EPS2_KP_900001058"."RX_TX_IX9" ON "EPS2_KP_900001058"."RX_TX" ("PRICE_CODE_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "EPS2_KP_900001058_INDEX" ;
Hope to get a solution to the above issue. Why no TRAIL records are being created for this 178th column in question. If i do for example the following SQL for a different column say "RETURNED_DATE", when the value of the RETURNED_DATE=NULL before the UPDATE is fired, the TRAIL records are being generated.
SQL>Update Eps2_Kp_900001058.Rx_Tx Set RETURNED_DATE=RETURNED_DATE Where Tx_Number=1014524 And Nhin_Store_Id=900001058 And Id=4575035;
SQL>COMMIT;

This looks like a trailing null issue. Sometimes Oracle decides not to write columns to the redo logs if they are null and they are the last column in the record. What version of Oracle is this? I can ask QA to look into this and see what can be done.
Thanks for the reply, but
1) The UPDATE done to a column i.e.POS_REFUND_DATE is NOT THE LAST column of the table=eps2_kp_900001058. Please see the DDL that is in this mail chain. So your observation is not right.
2) Also the TRAIL records does get generated if the following UPDATE is executed and the value of this column is NOT NULL prior to the firing of this UPDATE
Update Eps2_Kp_900001058.Rx_Tx Set Pos_Refund_Date=Pos_Refund_Date Where Tx_Number=1014524 And Nhin_Store_Id=900001058 And Id=4575035;
3) The TRAIL records does not get generted if the following UPDATE is done and the value of the column POS_REFUND_DATE is NULL before the UPDATE is fired.
Update Eps2_Kp_900001058.Rx_Tx Set Pos_Refund_Date=Pos_Refund_Date Where Tx_Number=1014524 And Nhin_Store_Id=900001058 And Id=4575035;
Very strange. Hope you can get me an answer.
Also opened an SR for this issue, the SR details are:
SR 3-7288541301 : TRAIL records are not getting generated for SELECTED UPDATE SQL statements - DB supplimental logging
4) Also the DB version is 11gR2, 11.2.0.3, 64 bit enterprise edition on AIX

Repairing permissions before and after updating software

What is the reason to repair permissions before and after updating software? This may sound like a stupid question to many of you, but I am new to computers and I am trying to learn how and why of some of the things of my PowerBook. I installed some updates without repairing permissions. Did I install some software updates the wrong way? Thank you.

This is a topic which will draw as many emphatic for and against responses as overnight shut down or not, defrag or not, optimise or not, and so on.
I agree with Neil. I believe that OS X has progressed sufficiently that repair permissions has become redundant and so I do not do it on any regular basis.
Some folk may refer you to an Apple Support Article 303602. That Article in its 4 May 2006 version, titled "Top 10 Tips to Keep Your Mac in Top Form" suggested Repair Permissions should be done "after upgrading or installing new software". The Article was however revised on 15 May 2006 to be titled "Top Tips to Keep Your Mac in Top Form" and the item on Repair Permissions [along with two other recommended maintenance tips] was removed. It is my view that the conclusion to be drawn here is that Apple no longer considers Repair Permissions to be a required maintenance procedure.
Many users have adopted a "Repair Permissions" mantra for a cure-all over several years. I dropped it sometime in 10.3.
But, to each his own.
HTH
TiPB 867 Mac OS X (10.4.6)

Oracle Alert: Access before and after update values of a table column

We have a requirement where a notification needs to be sent when 'END_DATE' attribute (column in a table X) is set, in an Oracle Applications form.
I have defined an Event based Oracle Alert which fires 'On Update' of the table X.
Could anyone please let me know as how to access the value of 'END_DATE' before and after update (i.e :new.END_DATE and :old.END_DATE) in the sql query of the alert.
The need to use the before update and after update values of the attribute 'END_DATE' is that if we add the condition END_DATE is not null, the alert is sent even if any other attrbutes are updated in the Oracle form which is not the intended behavior.
Appreciate any help.
Thanks

Hi
use selectionlistener for your first table then add clientlistener and serverlistener so that you will get the rows on click in back bean.
then get second table vo and and create and add row for that view object. add partial target to refresh your second table from back bean.
on click of save call commit operation.

My session in xmanager will die after 80% of database creation completes

Hi,
I am instaling oracle 10g on solaris through xmanager(X terminal), first i installed oracle 10g software only and i invoked dbca through xmanager after 80% of database creation completes my session will die i tried 4 times same problem, any body have faced the same problem, advice greately appreciated.
Thanks
Prakash

Did you check installation logs ?
oraInventory/logs/installActions<timestamp>.log
<ORACLE_HOME>/cfgtoollogs/oui/installActions<timestamp>.log

Everyone: This time repair your permissions before and after 10.4.8 update

Hello All,
Just a reminder for all those who are updating to OS 10.4.8.
While many people do ignore all the recommendations that we provide and still come through fine, please do consider observing the following to minimize your problems.
To insure the best chance of success, please consider downloading the Combo Updater for your computer instead of using Software update.
For PowerPC Mac's, this would be:
http://www.apple.com/support/downloads/macosx1048comboupdateppc.html
For Intel Macs, this would be:
http://www.apple.com/support/downloads/macosx1048comboupdateintel.html
The benefit of using the Combo Updater, is that it replaces all system files that have been changed since the last major release (in this case since 10.4.0).
So, if you have any system files that have become corrupted, the Combo Updater will very likely over-write those, and spare you the headaches that come from updating an operating system that has problems that just haven't come to the surface yet.
In many cases, you can have problems that have not come to the surface, and the "Delta" or Software update method will bring them out to bite you. The reason for this, is because the Delta / Software Update version only changes files that have changed since 10.4.7. And, it works more in a "patch" fashion. So, if there is a problem in one of the files being patched, then the update will cause you some major headaches.
Going with the larger "Combo" update over-writes almost all the System files with clean versions instead of just making patches. So, it is frequently much more successful.
Now, with that said, before you update, you should make sure your permissions are all set properly. If your permissions are wrong, then your update will likely have trouble.
So, go into "Disk Utility" in the Applications --> Utilities folder and repair your permissions.
Start by selecting your hard drive on the left window of Disk Utility. Then, go down and click on the "Repair Permissions" button. Once it's completed, then exit Disk Utility.
Now, it is also extremely important to make sure all running programs are closed before you install any system update. So, go ahead and restart your computer.
Restarting will make sure that all programs are closed, and that nothing weird is stuck in memory before you install.
If you have anti-virus programs running, then disable or deactivate them first (you don't want them interpreting this as unauthorized modification or it might prevent certain files from being updated).
Now, with your computer freshly restarted, install the Combo updater you downloaded.
When prompted, click on the "Restart" button when prompted.
Now, the computer will startup, but sit at the spinning wheel for several minutes. It will eventually restart again on it's own. And, finally, it will start-up all the way and you'll be back at your desktop.
Now, immediately go back to Disk Utility and repair permissions as you did in the previous step. You will likely see several permissions that have been repaired. In my case, I had dozens of CoreAudio, Widgets, and other permissions that needed repair. Once permissions have been repaired, go ahead and restart one last time. This makes sure that everything is set and then cleaned-up.
Once it reboots, begin using it and enjoy.
Now, this may sound like a lot. But, it really is simple. It just reads like a lot of stuff.
And, of course, you are free to ignore this and just install it however you like. Many people have their own ideas here. And, many people say you don't have to do anything to prepare. But, for those that have had huge problems in the past, these extra steps will usually save you the major headaches that tons of people inevitably have with every new update.
Anyway, I hope this helps to save at least a few of you any problems. If you don't agree with the ideas above, just ignore it and do as you like.
But, if you want a little extra piece-of-mind and a better chance at success, then please consider exercising this extra caution.
And, for the record, I have updated my machines to 10.4.8 (within minutes of the update being available) and it is working perfectly smooth on my systems.
I hope you find this helpful.

mhunter, thanks and good that you take the time and effort again to remind everyone that it does take an effort to do a major OS update, to ensure maximum stability.
So far my 10.4.8 Update is a-okay, and I have had many trouble-free updates since installing 10.4
I too practice rigourously and "religiously" before and after an OS or Security Update, but I normally use Software Update, equally successful:
1. Before Startup, UNPLUG all external devices, left only keyboard, mouse and internet connection, unless they are all wireless.
2. Startup, disable NAV if any, Repair Disk Permission. Restart again, Repair Permission again.
3. Do Software Update
4. Restart, Repair Permission
5. Shutdown, plug everything back
6. Startup Mac, use Mac
So far these steps have been keeping all my macs both at home and at work very very stable and healthy.
Maybe, just maybe if everyone here, all mac users were to follow these steps, yes they can be a hassle, yes they can take up some time, but then there will be less less complains and "blasts" at Apple, just because perhaps themselves have been too careless or negligance in performing updates.
Cheers

Should I repair permissions before or after updating to Mac OS X 10.7.2?

Hi,
Should I repair permissions before or after updating to Mac OS X 10.7.2? or should I fix permissions before and after the update?

This is not a routine maintenance. Upgrades can be screwed up if the system that is upgraded is screwed up. I believe in a "better safe than sorry" approach. If you repair permissions and the hard drive prior to an upgrade then if there be a problem perhaps that problem will not propagate to the new upgraded system. If there are no problems doing the repairs is harmless.
When it comes to the topic of permissions repairs there are many opinions but not much fact. In other words there doesn't appear to be a formal analysis of whether repairing permissions is only useful when a permissions problem arises. But there is a lot of anecdotal evidence suggesting that a repair both before and after a major system upgrade can reduce the risk of problems.
This is my opinion on the matter. I do not generally disagree with Niel or MacJack, but as I said I prefer to be safe rather than sorry.
Here's my general approach:
How to Install Lion Successfully - You must have Snow Leopard 10.6.7 or 10.6.8 Installed
A. Repair the Hard Drive and Permissions:
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. Then select Disk Utility from the Utilities. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.3.) if DW cannot fix the drive, then you will need to reformat the drive and reinstall Snow Leopard.
B. Make a Bootable Backup Using Restore Option of Disk Utility:
Open Disk Utility from the Utilities folder.
Select the destination volume from the left side list.
Click on the Restore tab in the DU main window.
Check the box labeled Erase destination.
Select the destination volume from the left side list and drag it to the Destination entry field.
Select the source volume from the left side list and drag it to the Source entry field.
Double-check you got it right, then click on the Restore button.
Destination means the backup volume. Source means the internal startup volume.
C. Important: Please read before installing:
If you have a FireWire hard drive connected, disconnect it before installing the update unless you will boot from this drive and install the update on it. Reconnect it and turn it back on after installation is complete and you've restarted.
You may experience unexpected results if you have installed third-party system software modifications, or if you have modified the operating system through other means. (This does not apply to normal application software installation.)
The installation process should not be interrupted. If a power outage or other interruption occurs during installation, use the standalone installer (see below) from Apple Downloads to update. While the installation is in progress do not use the computer.
D. To upgrade to Lion:
Purchase the Lion Installer from the Mac App Store. The download will start quickly. Lion is nearly 4 GBs so a fast internet connection is essential. Download time could run upwards of 4 hours depending upon network conditions and server demands at the time.
Boot From The Lion Installer which is located in your Applications folder.
Follow instructions for installation.

Pse crashing after database update.

hi there. some help would be amazing. i am kind of in panic mode to be honest.
my program is pse8 running on a PC with windows 7 (64 bit operating system)
i was having a hard time installing my photo actions, so i purchased graffi's add-o-matic.
i hated it because it would just insert a generic image where the thumbnails would be, so i never knew what action i was using until i hovered over it.
so, i googled, found out how to add photo actions manually. then i went in and deleted all of the ones add-o-matic had done before, got rid of the thumbnails and re-installed all my actions manually.
some of them looked great. the correct thumbnails were there, etc. more than half, however, did not look right. they were still showing add-o-matic's generic thumbnail or no thumbnail at all- just a black box where the action button would be.
i emailed the creator of the add-o-matic and he directed me to a workshop on his site about how to rebuild your database.
i did this:
Sometimes, though, something has blocked the database from finishing its update (you started working too soon while the database is still rebuilding in the background is the most common reason). Sometimes you simply have to manually force a rebuild of the database. It's fairly simple to do, but it does take a good 15 or 20 minutes to complete. Here's how to do that in Photoshop Elements:
(By the way, the file paths below are for Windows 7 & Vista - if you're using XP, substitute C:\Documents and Settings\All Users\Application Data for everywhere you see C:\Program Data\ )
Turn on hidden folders' visibility first by clicking Start>Control Panel>Folder Options, and choose the View tab. Scroll down to the section concerning viewing hidden files and folders, and toggle it ON. Click OK enough times to exit that dialog.
Then navigate to C:\Program Data\Adobe\Photoshop Elements\#.#
and locate the file "ThumbDatabase.db3" - rename it "ThumbDatabase.db3.OLD".
Next, navigate to
C:\Program Data\Adobe\Photoshop Elements\#.#\Locale\en_US
and rename the database file there, too, from "MediaDatabase.db3" to "MediaDatabase.db3.OLD"
*Quit all other programs (email, web browser, etc.) and restart Elements.
Your entire database will be rebuilt, and this will take a bit of time (around 15 ~ 20 minutes or so, maybe a bit more or less depending on your computer's speed, how many other utilities are running, how much stuff you've added to Elements, etc.)
When it finishes, restart Elements again, and all your menus should appear populated.
then when i went to open pse again, it just keeps crashing over and over and over.
i have uninstalled and reinstalled. cleaned it up with a registry cleaner, etc and i cannot get pse to stop crashing.
can someone please help me. this is so horrible!
thank you!

Go to http://www.thexlab.com/faqs/faqs.html and start with Multiple applications quit unexpectedly or fail to launch. Also, read Installing software updates before doing any more updates. I normally would say boot into your bootable backup, erase the volume you updated, and reinstall, but I don't get the inkling that you have one.

PeopleTools update before or after database creation

Similar Messages

Maybe you are looking for