Dml error logging for tables in 10.2.0.5

Hi experts,
I have problems loading error records into the shadow table specified in the configuration window for tables. Upon executing the mapping, the execution results show warnings with the error records but these records were not moved to the shadow/error table.
The actual scenario is: I specified a non-null data rule on the supplier_code column in the supplier table. Inside the mapping where I used this supplier table, I choose the option "Move to error" for this non-null data rule. Upon executing, it seems that owb treats these as warnings and not errors and thus did not propagate them to the error table. Anyone has any suggestion as to how to make use of the error tables in owb?

DML error logging is generated for set-based PL/SQL mappings if the following conditions are satisfied:
1. the Error table name property is set for the operator (table/view/mv)
2. the PL/SQL Generated Mode of the module that contains the mapping is set to 10gR2 and above or Default.
If the value is set to Default, ensure that location associated with the module has the Version set to 10.2 or above.
When you use a data object in a mapping, the Error Table Name property for this data object is derived from the shadow table name property of the data object . If you modify the error table name of a data object (using the shadow table name property), you must synchronize all the operators bound to this data object.
If you are still facing the issue then provide your email and I can send a simple example of data rule mapping in OWB 10.2.0.5
Sutirtha

Similar Messages

  • DML Error Logging for underlying tables autocreated for dimensions

    Hi,
    I have problems with logging errors during mapping for underlying tables that are automatically generated for creating dimensions. I know that DML Error Logging is supposed to work only on tables, views and materialized views, and I have tried it out using a pure table in a mapping without any reference to a dimension and specifying the error table name for it. This works perfectly. The error rows were captured correctly in the error table and the correct rows were also loaded successfully to the target table.
    However when it comes to mapping to a dimension, I have some issues with that. I specified the shadowtable name for the underlying table(right clicking on the table in design center and then choosing configure), and after deploying I did check that the error table/shadow table and also the target table were indeed created in the database.
    The problem lies now in the mapping because I am actually mapping to a dimension and not the underlying table the dimension references to. It seems that the mapping did not manage to capture details of the error table for the underlying table that the dimension was referencing to and thus were unable to capture the errors. Only the corrected rows get loaded and there were no error messages during the loading that suggests that the incorrect rows were detected.
    Would appreciate some assistance here.
    Thanks!
    WY

    Hi
    The DML error logging feature in 10gR2 and 11gR1 was restricted purely to tables, so the dimension operator did not support it. This is now supported in OWB 11gR2 (plus there is the orphan management functionality).
    Cheers
    David

  • DML Error logging for Update statement

    Hello,
    I am facing a problem with regard to DML Error logging with Update statement .
    oracle : 10.2
    I am executing following DML update:
    BEGIN
    UPDATE
    table_1  a
    SET a.Exp_DATE =a.EFF_DATE
    WHERE  a.col_a1 != (SELECT b.colb1
                         FROM table_2  b
                         WHERE  a.msisdn =b.msisdn )
    LOG ERRORS INTO table_1_ERR REJECT LIMIT UNLIMITED;                        
    END ;    I was expecting that "ORA-01427: single-row subquery returns more than one row" would be captured in LOG error table "table_1_err"
    but instead I got run time error and whole dml was rolled back.
    Please let me know whether this exception is not captured by DML error logging.
    Thanks,
    Abhishek

    *Oracle logs the following errors during DML operations:** Column values that are too large.
    * Constraint violations (NOT NULL, unique, referential, and check constraints).
    * Errors raised during trigger execution.
    * Errors resulting from type conversion between a column in a subquery and the corresponding column of the table.
    * Partition mapping errors.
    >
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14223/transform.htm#sthref777

  • Use global temp table for DML error logging

    our database is 11.2.0.4 enterprise edition on solaris 10
    we are wondering if anyone has an opinion of or has done this before, to use a global temp table for DML error logging. We have a fairly busy transactional database with 2 hot tables for inserts. The regular error table created with dbms_errlog has caused many deadlocks which we don't quite understand yet. we have thought using global temp table for the purpose, and that seemed to work, but we can't read error from the GTT, the table is empty even reading from the same session as inserts. Does anyone have an idea why?
    Thanks

    The insert into the error logging table is done with a recursive transaction therefore it's private from your session which is doing the actual insert.
    Adapted from http://oracle-base.com/articles/10g/dml-error-logging-10gr2.php
    INSERT INTO dest
    SELECT *
    FROM  source
    LOG ERRORS INTO err$_dest ('INSERT') REJECT LIMIT UNLIMITED;
    99,998 rows inserted.
    select count(*) from dest;
      COUNT(*)
        99998
    SELECT *
    FROM  err$_dest
    WHERE  ora_err_tag$ = 'INSERT';
    1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    1000        Description for 1000
    1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    10000        Description for 10000
    1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    1000        Description for 1000
    1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    10000        Description for 10000
    rollback;
    select count(*) from dest;
      COUNT(*)
            0
    SELECT *
    FROM  err$_dest
    WHERE  ora_err_tag$ = 'INSERT';
    1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    1000        Description for 1000
    1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    10000        Description for 10000
    1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    1000        Description for 1000
    1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    10000        Description for 10000

  • DML Error logging table in Set base mode

    Hi all,
    In ETL data errors can be handled thru error logging table. Like this example given in the document-
    INSERT /*+ APPEND PARALLEL */
    INTO sales SELECT product_id, customer_id, TRUNC(sales_date), 3,
    promotion_id, quantity, amount
    FROM sales_activity_direct
    LOG ERRORS INTO sales_activity_errors('load_20040802')
    REJECT LIMIT UNLIMITED
    In this example bulk loading is possible even in the presence of errors. The data errors will go in table 'Sales_activity_errors'.
    I want to generate this kind of coding in OWB in set base mode. For that i have to create a error logging table in target schema. How can I reference this table in a mapping? can it be done by shadow table? It's a very important feature in ETL for bulk loading. Is it available in OWB in set based mode?
    Guyzz please check this out and help me..
    Regards,
    Sumanta

    Hi,
    I am not sure if the DML error logging method is avaliable to be used in OWB 10g R2. You can use the data rule method. Create the data rules on the target table. Deploy it from OWB. Create your mappings and then execute them. Two insert statements will be generated. One for loading the target table for loading records where no rules are violated. The other for loading the <target table>_ERR for loading records where one or more error rules are violated.
    Both these statements do a bulk loading. So your purpose will be solved.
    Again you can use the splitter method that has already been mentioned.
    Regards
    -AP

  • DML Error Logging with multiple tables = OALL8

    I have a mapping that, via a splitter, loads 3 tables. This mapping works perfectly.
    Recently we upgraded to OWB 10.2.0.3 so we decided to make use of the new feature of DML error logging. So three error-tables where created and the "error table name" property of each table was entered. When re-creating this mapping in the database the following errors occur: "State of OALL8 is inconsistent", "No more data to read from Socket" (translated from dutch). When removing the value from the "error table name" property again, the mapping can be recreated again.
    What am I doing wrong? Have I run into a bug?

    Which database version are you using?
    Also not sure when exactly the error occurs, when you deploy the map...or when you execute the map? Can you describe as simple a scenario for it to fail that you can?
    I did find a bug 5942415 which was to do with this area..worth checking anyway.
    Cheers
    David

  • DML ERROR LOGGING STATEMENT FAILS FOR MULTITABLE INSERT

    When I use a simple expression in my dml error logging statement for a multitable insert I get 'end of file on communication channel' on the compile(in all guis tested). It works fine without the simple expression for the multitable insert. The simple expression works ok with a single table insert.
    example:
    this works ok for single table insert and blows up on multitable inserts:
    LOG ERRORS INTO ERR$_INVOICE (TO_CHAR(SYSDATE,'YYYYMMDD HH:MI:SS')) REJECT LIMIT UNLIMITED;
    this works ok for both:
    LOG ERRORS INTO ERR$_CINVOICE REJECT LIMIT UNLIMITED;
    any ideas?

    No version number, no DDl, and no DML. No help is possible.
    Complete version information and a demo that people can run to duplicate your situation will increase the chance of getting help.
    I, for example, have no idea what you intend with the statement multitable insert. Is this a reference to INSERT ALL or INSERT FIRST or some other syntax?

  • DML Error Logging Tables?

    How can I use DML Error Logging Tables with OWB10gR2 (in tab-definition and mappings)?
    btw: what really is a shadow-table?

    Hi,
    What you can do to solve this is to add a Pre-mapping to your mapping which calls a procedure that alters the constraint on the target table in which you use the "EXCEPTIONS INTO <error_table> " clause.
    like:
    PROCEDURE "ENABLE_CONSTR_WITH_EXCEPTIONS"("P_TABLE" IN VARCHAR2,  "P_CONSTRAINT" IN VARCHAR2) IS
    v_table            varchar2(30) := p_table;
    v_constraint          varchar2(30) := p_constraint;
    v_command           varchar2(200);
    e_CannotValidate      exception;
    PRAGMA EXCEPTION_INIT(e_CannotValidate, -2437);
    -- main body
    BEGIN
    /* Enable Constraint and write error into exception table */
      BEGIN
        v_command := 'ALTER TABLE ' || v_table || ' ENABLE CONSTRAINT '|| v_constraint ||' EXCEPTIONS INTO exceptions';
        execute immediate (v_command);
        commit;
      END;
        EXCEPTION
            WHEN e_CannotValidate THEN
               -- In my case when Unique Constraints are violated I will delete the duplicates.
               DELETE_DUPLICATES(v_table, v_constraint);
            WHEN OTHERS THEN
                NULL;  -- enter any exception code here
    END;
    -- End of ENABLE_CONSTR_WITH_EXCEPTIONS;Greetz,
    Ilona Tielke

  • Limitation on DML error logging

    Can someone please advise what is not supported by DML error logging which was introduced in Oracle 10g?
    one Oracle document says "You cannot track errors in the error logging table for LONG, LOB, or object type columns".
    One says only non-scalar columns, like datatime is not support.
    Another one says it doesn't support nested table.
    Anyone has a more complete list of limitation?
    Thanks!
    Edited by: user611482 on Feb 9, 2010 3:32 PM

    PLease read the following,
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tables.htm#sthref2234
    HTH
    Aman....

  • Alternative to DML Error Logging

    I am supposed to catch invalid records in error table with the ORA exception. I am using 10g. Using DML Error logging i cannot catch primary key violations. Using for loop it will be very slow because there are lots of records. How to catch invalid records with the ORA exception
    Thanks

    user637544 wrote:
    Using DML Error logging i cannot catch primary key violations.You can't use DML Error Logging future, because:
    The DML error logging functionality is not invoked when:
    Deferred constraints are violated.
    Direct-path INSERT or MERGE operations raise unique constraint or index violations.
    UPDATE or MERGE operations raise a unique constraint or index violation.
    Kamran Agayev A. (10g OCP)
    http://kamranagayev.wordpress.com

  • DML Error logging with delete restrict

    Hi,
    I am trying to log all DML errors while performing ETL process. We encountered a problem in the process when one of the on delete cascade is missing in child tables but I was curious to know why we got that exception to the calling environment because we are logging all DML errors in err$_ tables. Our expectation is when we get child record found violation then that error will be logged into ERR$_ tables and process will carry on without any interruption but it interrupted in the middle and terminated. I can illustrate with below example
    T1 -> T2 -> T3
    T1 is parent and it is s root
    Create table t1 (id number primary key, id2 number);
    Create table t2(id number references t1(id) on delete cascade, id2 number);
    create table t3 (id number references t2(id)); -- Missing on delete cascade
    insert into t1 as select level, level from dual connect by level < 20;
    insert into t2 as select level, level from dual connect by level < 20;
    insert into t3 as select level from dual connect by level < 20;
    exec dbms_errlog(t1);
    exec dbms_errlog(t2);
    exec dbms_errlog(t3);
    delete from t1 where id = 1 log errors into err$_t1 reject limit unlimited;   -- Child record found violation due to t3 raised but I am expecting this error will be trapped in log tables.
    delete from t2 where id =1 log errors into err$_t2 reject limit unlimited; -- Got the same error child record violation. My expectation error will be logged into log tables.
    I am using Oracle 11gR2.
    Also, Please let me know if there is any restrictions to use DML error logging in DBMS_PARALLEL_EXECUTE.
    Please advise
    Thanks,
    Umakanth

    What is the error you want me to fix? Missing on delete cascade?
    The Code you posted has multiple syntax errors and can't possibly run. You should post code that actually works.
    My expectation is all the DML errors will be logged into error logging tables even if it is child record found violation.
    delete from t1 where id = 1 log errors into err$_t1 reject limit unlimited;  -- Child record found violation due to t3 raised but I am expecting this error will be trapped in log tables.
    delete from t2 where id =1 log errors into err$_t2 reject limit unlimited; -- Got the same error child record violation. My expectation error will be logged into log tables.
    DML error logging logs DATA. When you delete from T1 there is an error because the T2 child record can NOT be deleted. So the T1 row that was being deleted is logged into the T1 error log table. The request was to delete a T1 row so that is the only request that failed; the child rows in T2 and T3 will not be put into log tables.
    Same when you try to delete from T2. The T3 child record can NOT be deleted so the T2 row that was being deleted is logged into the T2 error log table.
    The exceptions that occur are NOT logged, only the data that the DML could not be performed on.
    After I fixed your code your example worked fine for me and logged into the DML error tables as expected. But I wasn't doing it from a client.

  • DML error logging in OWB

    Hi,
    i am getting small problems with OWB regarding DML error logging. i was followed this link
    http://blogs.oracle.com/warehousebuilder/newsItems/viewFullItem$184
    i was created error table using DBMS_ERRLOG.CREATE_ERROR_LOG and i was assigned that table name in error table name property.
    * the Error table name property is set for the operator (table/view/mv)
    * the PL/SQL Generated Mode of the module that contains the mapping is set to 10gR2
    and above or Default.
    i was followed according to the instruction but i am not able to get desired output. can any one suggest me where i am wrong.
    i am using set based PL/SQL mapping.
    warehouse builder repository 10.2.0.1.0
    regards,
    kumar

    i am also facing same problem. is there any way to handle errors in 10.2.0.1.
    same as above. capture all the failed records in to error table in 10.2.0.1
    Regards,
    Jyothy

  • Error logging for data rules in owb11gr2

    Hi all,
    I was playing around with error logging for data rules and I realized that when an error gets logged into the error table for failing a particualar data rule for a table, some of the columns in the error table such as ORA_ERR_NUMBER$, ORA_ERR_MESG$, ORR_ERR_OPTYP$ were not filled in. Why is this so? Is there anyway to populate these fields as well when a row gets populated in? This is because the optype field may be useful to identify the operation type of the erronous row.
    ALso, does anyone know whether the error table for dimensions work correctly? I replicate the portion of the mapping flow that goes to my dimension and even though the errornous row gets logged into the error table, the ERR$$$_OPERATOR_NAME for that row did not show the dimension object but instead show another of my table operator in the mapping. Pretty bewildered as to why this is the case.

    The cube operator in 11gR2 also supports DML error logging (as well as orphan management handling). This is enabled by setting the property 'DML Error table name' (in group Error table) on the Cube operator inside the mapping. The error table specified will be created when the mapping is deployed (if you specify an existing one the error is trapped).
    The DML error handling will catch physical errors on the load of the fact.
    Cheers
    David

  • SQL reporting - An internal error occurred on the report server. See the error log for more details. (rsInternalError)

    I have created an RDL file programatically. When I execute the code I get the error as mentioned below:
    Error: Sub report cannot be shown.
    An internal error occurred on the report server. See the error log for more details. (rsInternalError)
    When I copy and paste the code of RDL file into new RDL file and try to preview the output I get correct result.
    Note: The new RDL file does not give any error if the output is seen using preview tab but it gives the error only when executed from report viewer or from internet explorer.
    Any Suggestion/feedback is highly appreciated.
    Thank You.
    The code of the sample RDL is shown below:
    <?xml version="1.0" encoding="utf-8"?>
    <Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
      <DataSources>
        <DataSource Name="DataSource1">
          <DataSourceReference>DataSource1</DataSourceReference>
          <rd:DataSourceID>fe4806ee-0358-4a87-b764-ac5de049545e</rd:DataSourceID>
        </DataSource>
      </DataSources>
      <BottomMargin>0.25in</BottomMargin>
      <RightMargin>0.25in</RightMargin>
      <PageWidth>11in</PageWidth>
      <ReportParameters>
        <ReportParameter Name="machine_id">
          <DataType>String</DataType>
          <Prompt>machine_id</Prompt>
        </ReportParameter>
        <ReportParameter Name="from_date">
          <DataType>String</DataType>
          <AllowBlank>true</AllowBlank>
          <Prompt>From Date</Prompt>
        </ReportParameter>
        <ReportParameter Name="to_date">
          <DataType>String</DataType>
          <AllowBlank>true</AllowBlank>
          <Prompt>To Date</Prompt>
        </ReportParameter>
      </ReportParameters>
      <rd:DrawGrid>true</rd:DrawGrid>
      <InteractiveWidth>8.5in</InteractiveWidth>
      <rd:SnapToGrid>true</rd:SnapToGrid>
      <Body>
        <ReportItems>
          <Table Name="table1">
            <DataSetName>Main_Report</DataSetName>
            <TableGroups>
              <TableGroup>
                <Header>
                  <TableRows>
                    <TableRow>
                      <TableCells>
                        <TableCell>
                          <ReportItems>
                            <Textbox Name="textbox2">
                              <rd:DefaultName>textbox2</rd:DefaultName>
                              <ZIndex>1</ZIndex>
                              <Style>
                                <TextAlign>Left</TextAlign>
                                <PaddingLeft>2pt</PaddingLeft>
                                <PaddingBottom>2pt</PaddingBottom>
                                <PaddingRight>2pt</PaddingRight>
                                <PaddingTop>2pt</PaddingTop>
                              </Style>
                              <CanGrow>true</CanGrow>
                              <Value>=Fields!syscode.Value</Value>
                            </Textbox>
                          </ReportItems>
                        </TableCell>
                      </TableCells>
                      <Height>0.25in</Height>
                    </TableRow>
                  </TableRows>
                  <RepeatOnNewPage>true</RepeatOnNewPage>
                </Header>
                <Grouping Name="table1_Group1">
                  <PageBreakAtEnd>true</PageBreakAtEnd>
                  <GroupExpressions>
                    <GroupExpression>=Fields!syscode.Value</GroupExpression>
                  </GroupExpressions>
                </Grouping>
              </TableGroup>
            </TableGroups>
            <Details>
              <TableRows>
                <TableRow>
                  <TableCells>
                    <TableCell>
                      <ReportItems>
                        <Subreport Name="subreport1">
                          <Parameters>
                            <Parameter Name="machine_id">
                              <Value>=Fields!machine_ip.Value</Value>
                            </Parameter>
                            <Parameter Name="syscode">
                              <Value>=Fields!syscode.Value</Value>
                            </Parameter>
                            <Parameter Name="from_date">
                              <Value>=Parameters!from_date.Value</Value>
                            </Parameter>
                            <Parameter Name="to_date">
                              <Value>=Parameters!to_date.Value</Value>
                            </Parameter>
                          </Parameters>
                          <ReportName>Holding_Summary_Multi_Period</ReportName>
                        </Subreport>
                      </ReportItems>
                    </TableCell>
                  </TableCells>
                  <Height>0.25in</Height>
                </TableRow>
              </TableRows>
            </Details>
            <TableColumns>
              <TableColumn>
                <Width>10.5in</Width>
              </TableColumn>
            </TableColumns>
            <Height>0.5in</Height>
          </Table>
        </ReportItems>
        <Height>0.75in</Height>
      </Body>
      <rd:ReportID>d0a1293a-e98c-4f75-9597-03426d2e7218</rd:ReportID>
      <LeftMargin>0.25in</LeftMargin>
      <DataSets>
        <DataSet Name="Main_Report">
          <Query>
            <rd:UseGenericDesigner>true</rd:UseGenericDesigner>
            <CommandText>select account_syscode as syscode , 'display Name' as display_name , * from mars_customer_list
    where machine_ip = @machine_id</CommandText>
            <QueryParameters>
              <QueryParameter Name="@machine_id">
                <Value>=Parameters!machine_id.Value</Value>
              </QueryParameter>
            </QueryParameters>
            <DataSourceName>DataSource1</DataSourceName>
          </Query>
          <Fields>
            <Field Name="syscode">
              <rd:TypeName>System.Int64</rd:TypeName>
              <DataField>syscode</DataField>
            </Field>
            <Field Name="display_name">
              <rd:TypeName>System.String</rd:TypeName>
              <DataField>display_name</DataField>
            </Field>
            <Field Name="customer_syscode">
              <rd:TypeName>System.Int64</rd:TypeName>
              <DataField>customer_syscode</DataField>
            </Field>
            <Field Name="account_syscode">
              <rd:TypeName>System.Int64</rd:TypeName>
              <DataField>account_syscode</DataField>
            </Field>
            <Field Name="machine_ip">
              <rd:TypeName>System.String</rd:TypeName>
              <DataField>machine_ip</DataField>
            </Field>
          </Fields>
        </DataSet>
      </DataSets>
      <Code>Shared offset As Integer
    Public Function GetPN(reset As Boolean, pagenumber As Integer) As Integer
      If reset
        offset = pagenumber - 1
      End If
      Return pagenumber - offset
    End Function
    </Code>
      <Width>10.5in</Width>
      <InteractiveHeight>11in</InteractiveHeight>
      <Language>en-US</Language>
      <PageFooter>
        <ReportItems>
          <Image Name="image1">
            <Sizing>Fit</Sizing>
            <Left>8.875in</Left>
            <MIMEType />
            <Width>1.5in</Width>
            <Source>External</Source>
            <Style />
            <Value>bottom_right_logo.gif</Value>
          </Image>
        </ReportItems>
        <Height>0.5in</Height>
        <PrintOnLastPage>true</PrintOnLastPage>
        <PrintOnFirstPage>true</PrintOnFirstPage>
      </PageFooter>
      <TopMargin>0.5in</TopMargin>
      <PageHeight>8.5in</PageHeight>
    </Report>

    i created a SSRS report with shared datasets and uploaded rdl files and rsd files , while trying to map rdl file with data sets i am getting an error
    when i click on manage for .rdl file, its throwing error , as
    "An internal error occurred on the report server. See the error log for more details. (rsInternalError)
    Object reference not set to an instance of an object.
    please help me with this

  • OWB 10gR2 Does not support DML Error Logging

    I've just had this confirmed by support.
    So Oracle's key ETL tool does not support 10gR2s key ETL feature DML Logging.
    So far set based loads on large volume databases you are going to find yourself being tripped over into row by row processing.
    I find this staggering.
    Has anyone else found this?

    Oracle has come back to us saying that
    "DML error logging feature is not supported for distributed DML."

Maybe you are looking for

  • Another iMac Freezing Issue - pls help a newbie out

    I understand this problem is not uncommon - I've been trying to read the many threads I see on the issue. However, most posts outline problems, suggestions are made, but then reported to not work. Also, many threads are 2 years old. Could someone ple

  • Update 700 Sequence Files

    A couple years ago we created a template for all of our TestStand sequences which included the "Setup" and "Cleanup" using discrete subsequence calls and to simplify and add functionality I've created a new Master Initialize and Cleanup OLD FORMAT:  

  • New HDD for Inspiron Duo

    Hello, my Inspiron Duo's HDD is defective and I can't recover it. I have a new HDD but I don't know how to install Windows in it, as the Duo BIOS doesn't support boot by an USB device and it doesn't have a CD/DVD-reader. How can I replace the HDD and

  • How to move Preferences and Share Email Contacts?

    After a recent total system crash I have had to reinstall my PSE (still 4.0).  From an earlier backup of my hard drive I have been able to recover my photos, tags, collections, etc.  However, my Preferences, Share>Email>Contacts, (and I know not what

  • User permissions stopping apps from running

    I have an old Indigo iMac which I'm giving away to a family with Primary (elementary) aged children. It is running 10.3.9, has a 500MHz processor and 256MB of RAM. I set up an admin user and then two limited users for the kids. Everything runs correc