10.1.0.4 GeoRaster Users Warning

When you apply the 10.1.0.4 patch, the MDSYS.SDO_GEOR_SYSDATA_TABLE is dropped and recreated in the MDSYS schema. This will wipe out your GeoRaster entries for data you have loaded.
Before you apply the 10.1.0.4 patch, if you have GeoRaster data loaded:
Connect as a privileged user.
Alter session set current_schema = mdsys;
create table temp_geor_sysdata as select * from SDO_GEOR_SYSDATA_TABLE;
Apply the patch.
After applying the patch and following the postinstallation instructions:
Connect as a privileged user.
Alter session set current_schema = mdsys;
insert into SDO_GEOR_SYSDATA_TABLE (select * from temp_geor_sysdata);

Chris - and there's the problem. I didn't properly record the error at the time (except that it was an ORA-00600 error, and hence a "call Oracle support" one) as I thought the whole script was going to fall over. It completed OK after that and seems to be working ok now. When I get a chance I'll try it again, but it means doing a reinstall as I think the uninstall script doesn't take things exactly back to where they were before.
Mark

Similar Messages

  • New FCE 4.0 User - "Warning - Dropped Frames"

    Okay, so... I've captured some video that I'm trying to speed up significantly (1000%+). When I play it back I get a warning after 4-5 seconds of play that reads -
    "One or more frames were dropped during playback"
    Then it says to do one of the following:
    -Increase Disk Speed
    -Decrease # of RT Layers
    -Limit RT Bandwidth in User Preferences
    The dialogue also suggests I turn off "Unlimited RT" & lower the compression data rate. Sadly I'm not exactly sure what to do or what all this means. Is this even really a problem? What should I do?
    Also... I'm using a Sony DCR-TRV22 MiniDV Handycam. I have FCE set to DV-NTSC. I wasn't sure what the differences between that and the 32KHz variations were. Could someone explain?
    Thanks.

    The AUDIO can usually be recorded as either 12bit or 16bit.
    If it is 12bit you use the "DV-NTSC 32KHz" Easy Setup otherwise you might get sync problems.
    However, this is unlikely to cause dropped frames.
    Usually you are taking the computer to its limits. Try rendering your clip and it should playback OK.

  • How to get All Users from OID LDAP

    Hi all,
    I have Oracle Internet Directory(OID) and have created the users in it manually.
    Now I want to extract all the users from OID. How can I get Users from OID??
    Any response will be appritiated. If some one could show me demo code for that I shall be greatful to you.
    Thanks and reagards
    Pravy

    hi,
    the notes from metalink:
    bgards
    elvis
    Doc ID: Note:276688.1
    Subject: How to copy (export/import) the Portal database schemas of IAS 9.0.4 to another database
    Type: BULLETIN
    Status: PUBLISHED
    Content Type: TEXT/X-HTML
    Creation Date: 18-JUN-2004
    Last Revision Date: 05-AUG-2005
    How to copy (export/import) Portal database schemas of IAS 9.0.4 to another database
    Note 276688.1
    Download scripts Unix: Attachment 276688.1:1
    Download Perl scripts (Unix/NT) :Attachment 276688.1:2
    This article is being delivered in Draft form and may contain errors. Please use the MetaLink "Feedback" button to advise Oracle of any issues related to this article.
    HISTORY
    Version 1.0 : 24-JUN-2004: creation
    Version 1.1 : 25-JUN-2004: added a link to download the scripts from Metalink
    Version 1.2 : 29-JUN-2004: Import script: Intermedia indexes are recreated. Imported jobs are reassigned to Portal. ptlconfig replaces ptlasst.
    Version 1.3 : 09-JUL-2004: Additional updates. Usage of iasconfig.xml. Need only 3 environment variables to import.
    Version 1.4 : 18-AUG-2004: Remark about 9.2.0.5 and 10.1.0.2 database
    Version 1.5 : 26-AUG-2004: Duplicate job id
    Version 1.6 : 29-NOV-2004: Remark about WWC-44131 and WWSBR_DOC_CTX_54
    Version 1.7 : 07-JAN-2005: Attached perl scripts (for NT/Unix) at the end of the note
    Version 1.8 : 12-MAY-2005: added a work-around for the WWSTO_SESS_FK1 issue
    Version 1.9 : 07-JUL-2005: logoff trigger and 9.0.1 database export, import in 10g database
    Version 1.10: 05-AUG-2005: reference to the 10.1.2 note
    PURPOSE
    This document explains how to copy a Portal database schema from a database to another database.
    It allows restoring the Portal repository and the OID security associated with Portal.
    It can be used to go in production by copying physically a database from a development portal to a production environment and avoid to use the export/import utilities of Portal.
    This note:
    uses the export/import on the database level
    allows the export/import to be done between different platforms
    The script are Unix based and for the BASH shell. They can be adapted for other platforms.
    For the persons familiar with this technics in Portal 9.0.2, there is a list of the main differences with Portal 9.0.2 at the end of the note.
    These scripts are based on the experience of a lot of persons in Portal 902.
    The scripts are attached to the note. Download them here: Attachment 276688.1:1 : exp_schema_904.zip
    A new version of the script was written in Perl. You can also download them, here: Attachment 276688.1:2 : exp_schema_904_v2.zip. They do exactly the same than the bash ones. But they have the advantage of working on all platforms.
    SCOPE & APPLICATION
    This document is intented for Portal administrators. For using this note, you need basic DBA skills.
    This notes is for Portal 9.0.4.x only. The notes for Portal 9.0.2 are :
    Note 228516.1 : How to copy (export/import) Portal database schemas of IAS 9.0.2 to another database
    Note 217187.1 : How to restore a cold backup of a Portal IAS 9.0.2 on another machine
    The note for Portal 10.1.2 is:
    Note 330391.1 : How to copy (export/import) Portal database schemas of IAS 10.1.2 to another databaseMethod
    The method that we will follow in the document is the following one:
    Export:
    - export of the 4 portal schemas of a database (DEV / development)
    - export the LDAP OID users and groups (optional)
    Install a new machine with fresh IAS installation (PROD / production)
    Import:
    - delete the new and empty portal schema on PROD
    - import the schemas in the production database in place of the deleted schemas
    - import the LDAP OID users and groups (optional)
    - modify the configuration such that the infrastructure uses the portal repository of the backup
    - modify the configuration such that the portal repository uses the OID, webcache and SSO of the new infrastructure
    The export and the import are divided in several steps. All of these steps are included in 2 sample scripts:
    export : exp_portal_schema.sh
    import : imp_portal_schema.sh
    In the 2 scripts, all the steps are runned in one shot. It is just an example. Depending of the configuration and circonstance, all the steps can be runned independently.
    Convention
    Development (DEV) is the name of the machine where resides the copied database
    Production (PROD) is the name of the machine where the database is copied
    Prerequisite
    Some prerequisite first.
    A. Environment variables
    To run the import/export, you will need 3 environment variables. In the given scripts, they are defined in 'portal_env.sh'
    SYS_PASSWORD - the password of user sys in the Portal database
    IAS_PASSWORD - the password of IAS
    ORACLE_HOME - the ORACLE_HOME of the midtier
    The rest of the settings are found automatically by reading the iasconfig.xml file and querying the OID. It is done in 'portal_automatic_env.sh'. I wish to write a note on iasconfig.xml and the way to transform it in usefull environment variables. But it is not done yet. In the meanwhile, you can read the old 902 doc, that explains the meaning of most variables :
    < Note 223438.1 : Shell script to find your portal passwords, settings and place them in environment variables on Unix >
    B. Definition: Cutter database
    A 'Cutter Database' is the term used to designate a Database created by RepCA or OUI and that contains all the schemas used by a IAS 9.0.4 infrastructure. Even if in most cases, several schemas are not used.
    In Portal 9.0.4, the option to install only the portal repository in an empty database has been removed. It has been replaced by RepCA, a tool that creates an infrastructure database. Inside all the infrastucture database schemas, there are the portal schemas.
    This does not stop people to use 2 databases for running portal. One for OID and one for Portal. But in comparison with Portal 9.0.2, all schemas exist in both databases even if some are not used.
    The main idea of Cutter database is to have only 1 database type. And in the future, simplify the upgrades of customer installation
    For an installation where Portal and OID/SSO are in 2 separate databases, it looks like this
    Portal 9.0.2 Portal 9.0.4
    Infrastructure database
    (INFRA_SID)
    The infrastructure contains:
    - OID (used)
    - OEM (used)
    - Single Sign-on / orasso (used)
    - Portal (not used)
    The infrastructure contains:
    - OID (used)
    - OEM (used)
    - Single Sign-on / orasso (used)
    - Portal (not used)
    Portal database
    (PORTAL_SID)
    The custom Portal database contains:
    - Portal (used)
    The custom Portal database (is also an infrastructure):
    - OID (not used)
    - OEM (not used)
    - Single Sign-on / orasso (not used)
    - Portal (used)
    Whatever, the note will suppose there is only one single database. But it works also for 2 databases installation like the one explained above.
    C. Directory structure.
    The sample scripts given inside this note will be explained in the next paragraphs. But first, the scripts are done to use a directory structure that helps to classify the files.
    Here is a list of important files used during the process of export/import:
    File Name
    Description
    exp_portal_schema.sh
    Sample script that exports all the data needed from a development machine
    imp_portal_schema.sh
    Sample script that import all the data into a production machine
    portal_env.sh
    Script that defines the env variable specific to your system (to configure)
    portal_automatic_env.sh
    Helper script to get all the rest of the Portal settings automatically
    xsl
    Directory containing all the XSL files (helper scripts)
    del_authpassword.xsl
    Helper script to remove the authpassword tags in the DSML files
    portal_env_unix.sql
    Helper script to get Portal settings from the iasconfig.xml file
    exp_data
    Directory containing all the exported data
    portal_exp.dmp
    export on the database level of the portal, portal_app, ... database schemas
    iasconfig.xml
    copy the name of iasconfig.xml of the midtier of DEV. Used to get the hostname and port of Webcache
    portal_users.xml
    export from LDAP of the OID users used by Portal (optional)
    portal_groups.xml export from LDAP of the OID groups used by Portal (optional)
    imp_log
    Directory containing several spool and logs files generated during the import
    import.log Log file generated when running the imp command
    ptlconfig.log
    Log generated by ptlconfig when rewiring portal to the infrastructure.
    Some other spool files.
    D. Known limitations
    The scripts given in this note have the following known limitations:
    It does not copy the data stored in the SSO schema: external applications definitions and the passwords stored for them.
    See in the post steps: SSO migration to know how to do.
    The ssomig command resides in the Infrastructure Oracle home. And all commands of Portal in the Midtier home. And practically, these 2 Oracle homes are most of the time not on the same machine. This is the reason.
    The export of the users in OID exports from the default user location:
    ldapsearch .... -b "cn=users,dc=domain,dc=com"
    This is not 100% correct. The users are by default stored in something like "cn=users,dc=domain,dc=com". So, if the users are stored in the default location, it works. But if this location (user install base) is customized, it does not work.
    The reason is that such settings means that the LDAP most of the time highly customized. And I prefer that the administrator to copy the real LDAP himself. The right command will probably depend of the customer case. So, I prefered not to take the risk..
    orclCommonNicknameAttribute must match in the Target and Source OID .
    The orclCommonNicknameAttribute must match on both the source and target OID. By default this attribute is set to "uid", so if this has been changed, it must be changed in both systems.
    Reference Note 282698.1
    Migration of custom Java portlets.
    The script migrates all the data of Portal stored in the database. If you have custom java portlet deployed in your development machine, you will need to copy them in the production system.
    Step 1 - Export in Development (DEV)
    To export a full Portal installation to another machine, you need to follow 3 steps:
    Export at the database level the portal schemas + related schemas
    Get the midtier hostname and port of DEV
    Export of the users and groups with LDAPSEARCH in 2 XML files
    A script combining all the steps is available here.
    A. Export the 4 portals schemas (DEV)
    You need to export 3 types of database schemas:
    The 4 portal schemas created by default by the portal installation :
    portal,
    portal_app,
    portal_demo,
    portal_public
    The schemas where your custom database portlets / providers resides (if any)
    - The custom schemas you have created for storing your portlet / provider code
    The schemas where your custom tables resides. (if any)
    - Your custom schemas accessed by portal and containing only data (tables, views ...)
    You can get an approximate list of the schemas: default portal schemas (1) and database portlets schemas (2) with this query.
    SELECT USERNAME, DEFAULT_TABLESPACE, TEMPORARY_TABLESPACE
    FROM DBA_USERS
    WHERE USERNAME IN (user, user||'_PUBLIC', user||'_DEMO', user||'_APP')
    OR USERNAME IN (SELECT DISTINCT OWNER FROM WWAPP_APPLICATION$ WHERE NAME != 'WWV_SYSTEM');
    It still misses your custom schemas containing data only (3).
    We will export the 4 schemas and your custom ones in an export file with the user sys.
    Please, use a command like this one
    exp userid="'sys/change_on_install@dev as sysdba'" file=portal_exp.dmp grants=y log=portal_exp.log owner=(portal,portal_app,portal_demo,portal_public)The result is a dump file: 'portal_exp.dmp'. If you are using a database 9.2.0.5 or 10.1.0.2, the database of the exp/imp dump file has changed. Please read this.
    B. Hostname and port
    For the URL to access the portal, you need the 2 following infos to run the script 'imp_portal_schema.sh below :
    Webcache hostname
    Webcache listen port
    These values are contained in the iasconfig.xml file of the midtier.
    iasconfig.xml
    <IASConfig XSDVersion="1.0">
    <IASInstance Name="ias904.dev.dev_domain.com" Host="dev.dev_domain.com" Version="9.0.4">
    <OIDComponent AdminPassword="@BfgIaXrX1jYsifcgEhwxciglM+pXod0dNw==" AdminDN="cn=orcladmin" SSLEnabled="false" LDAPPort="3060"/>
    <WebCacheComponent AdminPort="4037" ListenPort="7782" InvalidationPort="4038" InvalidationUsername="invalidator" InvalidationPassword="@BR9LXXoXbvW1iH/IEFb2rqBrxSu11LuSdg==" SSLEnabled="false"/>
    <EMComponent ConsoleHTTPPort="1813" SSLEnabled="false"/>
    </IASInstance>
    <PortalInstance DADLocation="/pls/portal" SchemaUsername="portal" SchemaPassword="@BR9LXXoXbvW1c5ZkK8t3KJJivRb0Uus9og==" ConnectString="cn=asdb,cn=oraclecontext">
    <WebCacheDependency ContainerType="IASInstance" Name="ias904.dev.dev_domain.com"/>
    <OIDDependency ContainerType="IASInstance" Name="ias904.dev.dev_domain.com"/>
    <EMDependency ContainerType="IASInstance" Name="ias904.dev.dev_domain.com"/>
    </PortalInstance>
    </IASConfig>
    It corresponds to a portal URL like this:
    http://dev.dev_domain.com:7782/pls/portalThe script exp_portal_schema.sh copy the iasconfig.xml file in the exp_data directory.
    C. Export the security: users and groups (optional)
    If you use other Single Sing-On uses than the portal user, you probably need to restore the full security, the users and groups stored in OID on the production machine. 5 steps need to be executed for this operation:
    Export the OID entries with LDAPSEARCH
    Before to import, change the domain in the generated file (optional)
    Before to import, remove the 'authpassword' attributes from the generated files
    Import them with LDAPADD
    Update the GUID/DN of the groups in portal tables
    Part 1 - LDAPSEARCH
    The typical commands to do this operation look like this:
    ldapsearch -h $OID_HOSTNAME -p $OID_PORT -X -b "cn=portal.040127.1384,cn=groups,dc=dev_domain,dc=com" -s sub "objectclass=*" > portal_group.xml
    ldapsearch -h $OID_HOSTNAME -p $OID_PORT -X -D "cn=orcladmin" -w $IAS_PASSWORD -b "cn=users,dc=dev_domain,dc=com" -s sub "objectclass=inetorgperson" > portal_users.xmlTake care about the following points
    The groups are stored in a LDAP directory containing the date of installation
    ( in this example: portal.040127.1384,cn=groups,dc=dev_domain,dc=com )
    If the domain of dev and prod is different, the exported files contains the name of the development domain in the form of 'dc=dev_domain,dc=com' in a lot of place. The domain name needs to be replaced by the production domain name everywhere in the files.
    Ldapsearch uses the option '- X '. It it to export to DSML files (XML). It avoids a problem related with common LDAP files, LDIF files. LDIF files are wrapped at 78 characters. The wrapping to 78 characters make difficult to change the domain name contained in the LDIF files. XML files are not wrapped and do not have this problem.
    A sample script to export the 2 XML files is given here in : step 3 - export the users and groups (optional) of the export script.
    Part 2 : change the domain in the DSML files
    If the domain of dev and prod is different, the exported files contains the name of the development domain in the form of 'dc=dev_domain,dc=com' in a lot of place. The domain name need to be replaced by the production domain name everywhere in the files.
    To do this, we can use these commands:
    cat exp_data/portal_groups.xml | sed -e "s/$DEV_DN/$PROD_DN/" > imp_log/portal_groups.xml
    cat exp_data/portal_users.xml | sed -e "s/$DEV_DN/$PROD_DN/" > imp_log/temp_users.xml
    Part 3 : Remove the authpassword attribute
    The export of all attributes from the all users has also exported an automatically generated attribute in OID called 'authpassword'.
    'authpassword' is a list automatically generated passwords for several types of application. But mostly, it can not be imported. Also, there is no option in ldapsearch (that I know) that allows removing an attribute. In place of giving to the ldapsearch command the list of all the attributes that is very long, without 'authpassword', we will remove the attribute after the export.
    For that we will use the fact that the DSML files are XML files. There is a XSLT in the Oracle IAS, in the executable '$ORACLE_HOME/bin/xml'. XSLT is a standard specification of the internet consortium W3C to transform a XML file with the help of a XSL file.
    Here is the XSL file to remove the authpassword tag.
    del_autpassword.xsl
    <!--
    File : del_authpassword.xsl
    Version : 1.0
    Author : mgueury
    Description:
    Remove the authpassword from the DSML files
    -->
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xml:output method="xml"/>
    <xsl:template match="*|@*|node()">
    <xsl:copy>
    <xsl:apply-templates select="*|@*|node()"/>
    </xsl:copy>
    </xsl:template>
    <xsl:template match="attr">
    <xsl:choose>
    <xsl:when test="@name='authpassword;oid'">
    </xsl:when>
    <xsl:when test="@name='authpassword;orclcommonpwd'">
    </xsl:when>
    <xsl:otherwise>
    <xsl:copy>
    <xsl:apply-templates select="*|@*|node()"/>
    </xsl:copy>
    </xsl:otherwise>
    </xsl:choose>
    </xsl:template>
    </xsl:stylesheet>
    And the command to make the transfomation:
    xml -f -s del_authpassword.xsl -o imp_log/portal_users.xml imp_log/temp_users.xmlWhere :
    imp_log/portal_users.xml is the final file without authpassword tags
    imp_log/temp_users.xml is the input file with the authpassword tags that can not be imported.
    Part 4 : LDAPADD
    The typical commands to do this operation look like this:
    ldapadd -h $OID_HOSTNAME -p $OID_PORT -D "cn=orcladmin" -w $IAS_PASSWORD -c -X portal_group.xml
    ldapadd -h $OID_HOSTNAME -p $OID_PORT -D "cn=orcladmin" -w $IAS_PASSWORD -c -X portal_users.xmlTake care about the following points
    Ldapadd uses the option ' -c '. Existing users/groups are generating an error. The option -c allows continuing and ignoring these errors. Whatever, the errors should be checked to see if it is just existing entries.
    A sample script to import the 2 XML files given in the step 5 - import the users and groups (optional) of the import script.
    Part 5 : Update the GUID/DN
    In Portal 9.0.4, the update of the GUID is taken care by PTLCONFIG during the import. (Import step 7)
    D. Example script for export
    Here is a example script that combines the 3 steps.
    Depending of you need, you will :
    or execute all the steps
    or just execute the 1rst one (export of the database users). It will be enough you just want to login with the portal user on the production instance.
    if your portal repository resides in a database 9.2.0.5 or 10.1.0.2, please read this
    you can download all the scripts here, Attachment 276688.1:1
    Do not forget to modify the script to your need and mostly add the list of users like explained in point A above.
    exp_portal_schema.sh
    # BASH Script : exp_portal_schema.sh
    # Version : 1.3
    # Portal : 9.0.4.0
    # History :
    # mgueury - creation
    # Description:
    # This script export a portal dump file from a dev instance
    # -------------------------- Environment variables --------------------------
    . portal_env.sh
    # In case you do not use portal_env.sh you have to define all the variables
    # For exporting the dump file only.
    # export SYS_PASSWORD=change_on_install
    # export PORTAL_TNS=asdb
    # For the security (optional)
    # export IAS_PASSWORD=welcome1
    # export PORTAL_USER=portal
    # export PORTAL_PASSWORD=A1b2c3de
    # export OID_HOSTNAME=development.domain.com
    # export OID_PORT=3060
    # export OID_DOMAIN_DN=dc=`echo $OID_HOSTNAME | cut -d '.' -f2,3,4,5,6 --output-delimiter=',dc='`
    # ------------------------------ Help function -----------------------------------
    function press_any_key() {
    if [ $PRESS_ANY_KEY_AFTER_EACH_STEP = "Y" ]; then
    echo
    echo Press enter to continue
    read $ANY_KEY
    else
    echo
    fi
    echo "------------------------------- Export ------------------------------------"
    # create a directory for the export
    mkdir exp_data
    # copy the env variables in the log just in case
    export > exp_data/exp_env_variable.txt
    echo "--------------------- step 1 - export"
    # export the portal users, but take care to add:
    # - your users containing DB providers
    # - your users containing data (tables)
    exp userid="'sys/$SYS_PASSWORD@$PORTAL_TNS as sysdba'" file=exp_data/portal_exp.dmp grants=y log=exp_data/portal_exp.log owner=(portal,portal_app,portal_demo,portal_public)
    press_any_key
    echo "--------------------- step 2 - store iasconfig.xml file of the MIDTIER"
    cp $MIDTIER_ORACLE_HOME/portal/conf/iasconfig.xml exp_data
    press_any_key
    echo "--------------------- step 3 - export the users and groups (optional)"
    # Export the groups and users from OID in 2 XML files (not LDIF)
    # The OID groups of portal are stored in GROUP_INSTALL_BASE that depends
    # of the installation date.
    # For the user, I use the default place. If it does not work,
    # you can find the user place with:
    # > exec dbms_output.put_line(wwsec_oid.get_user_search_base);
    # Get the GROUP_INSTALL_BASE used in security export
    sqlplus $PORTAL_USER/$PORTAL_PASSWORD@$PORTAL_TNS <<IASDB
    set serveroutput on
    spool exp_data/group_base.log
    begin
    dbms_output.put_line(wwsec_oid.get_group_install_base);
    end;
    IASDB
    export GROUP_INSTALL_BASE=`grep cn= exp_data/group_base.log`
    echo '--- Exporting Groups'
    echo 'creating portal_groups.xml'
    ldapsearch -h $OID_HOSTNAME -p $OID_PORT -X -s sub -b "$GROUP_INSTALL_BASE" -s sub "objectclass=*" > exp_data/portal_groups.xml
    echo '--- Exporting Users'
    echo 'creating portal_users.xml'
    ldapsearch -h $OID_HOSTNAME -p $OID_PORT -D "cn=orcladmin" -w $IAS_PASSWORD -X -s sub -b "cn=users,$OID_DOMAIN_DN" -s sub "objectclass=inetorgperson" > exp_data/portal_users.xml
    The script is done to run from the midtier.
    Step 2 - Install IAS in a new machine (PROD)
    A. Installation
    This note does not distinguish if Portal is sharing the same database than Single-Sign On and OID. For simplicity, I will speak only about 1 database. But I could also create a second infrastructure database just for the portal repository. This way is better for production system, because the Portal repository is only product used in the 2nd database. Having 2 separate databases allows taking easily backup of the portal repository.
    On the production machine, you need to install a fresh install of IAS 9.0.4. Take care to use :
    the same IAS patchset 9.0.4.1, 9.0.4.2, ...on the middle-tier and infrastruture than in development
    and same characterset than in development (or UTF8)
    The result will be 2 ORACLE_HOMES and 1 infrastructure database:
    the ORACLE_HOME of the infrastructure (SID:infra904)
    the ORACLE_HOME of the midtier (SID:ias904)
    an infrastructure database (SID:asdb)
    The empty new Portal install should work fine before to go to the next step.
    B. About tablespaces (optional)
    The size of the tablespace of the production should match the one of the Developement machine. If not, the tablespace will autoextend. It is not really a concern, but it is slow. You should modify the tablespaces for to have as much space on prod and dev.
    Also, it is safer to check that there is enough free space on the hard disk to import in the database.
    To modify the tablespace size, you can use Oracle Entreprise Manager console,
    On Unix, . oraenv
    infra904oemapp dbastudio
    On NT Start/ Programs/ Oracle Application server - infra904 / Enterprise Manager Console
    Launch standalone
    Choose the portal database (typically asdb.domain.com)
    Connect with a DBA user, sys or system
    Click Storage/Tablespaces
    Change the size of the PORTAL, PORTAL_DOC, PORTAL_LOGS, PORTAL_IDX tablespaces
    C. Backup
    It could be a good idea to take a backup of the MIDTIER and INFRASTRUCTURE Oracle Homes at that point to allow retesting the import process if it fails for any reason as much as you want without needing to reinstall everything.
    Step 3 - Import in production (on PROD)
    The following script is a sample of an Unix script that combines all the steps to import a portal repository to the production machine.
    To import a portal reporistory and his users and group in OID, you need to do 8 things:
    Stop the midtier to avoid errors while dropping the portal schema
    SQL*Plus with Portal
    Drop the 4 default portal schemas
    Create the portal users with the same passwords than the just deleted users and give them grants (you need to create your own custom shemas too if you have some).
    Import the dump file
    Import the users and groups into OID (optional)
    SQL*Plus with SYS : Post import changes
    Recompile everything in the database
    Reassign the imported jobs to portal
    SQL*Plus with Portal : Post import changes
    Recreate the Portal intermedia indexes
    Correct an import errror on wwsrc_preference$
    Make additional post import changes, by updating some portal tables, and replacing the development hostname, port or domain by the production ones.
    Rewire the portal repository with ptlconfig -dad portal
    Restart the midtier
    Here is a sample script to do this on Unix. You will need to adapt the script to your needs.
    imp_portal_schema.sh
    # BASH Script : imp_portal_schema.sh
    # Version : 1.3
    # Portal : 9.0.4.0
    # History :
    # mgueury - creation
    # Description:
    # This script import a portal dump file and relink it with an
    # infrastructure.
    # Script to be started from the MIDTIER
    # -------------------------- Environment variables --------------------------
    . portal_env.sh
    # Development and Production machine hostname and port
    # Example
    # .._HOSTNAME machine.domain.com (name of the MIDTIER)
    # .._PORT 7782 (http port of the MIDTIER)
    # .._DN dc=domain,dc=com (domain name in a LDAP way)
    # These values can be determined automatically with the iasconfig.xml file of dev
    # and prod. But if you do not know or remember the dev hostname and port, this
    # query should find it.
    # > select name, http_url from wwpro_providers$ where http_url like 'http%'
    # These variables are used in the
    # > step 4 - security / import OID users and groups
    # > step 6 - post import changes (PORTAL)
    # Set the env variables of the DEV instance
    rm /tmp/iasconfig_env.sh
    xml -f -s xsl/portal_env_unix.xsl -o /tmp/iasconfig_env.sh exp_data/iasconfig.xml
    . /tmp/iasconfig_env.sh
    export DEV_HOSTNAME=$WEBCACHE_HOSTNAME
    export DEV_PORT=$WEBCACHE_LISTEN_PORT
    export DEV_DN=dc=`echo $OID_HOSTNAME | cut -d '.' -f2,3,4,5,6 --output-delimiter=',dc='`
    # Set the env variables of the PROD instance
    . portal_env.sh
    export PROD_HOSTNAME=$WEBCACHE_HOSTNAME
    export PROD_PORT=$WEBCACHE_LISTEN_PORT
    export PROD_DN=dc=`echo $OID_HOSTNAME | cut -d '.' -f2,3,4,5,6 --output-delimiter=',dc='`
    # ------------------------------ Help function -----------------------------------
    function press_any_key() {
    if [ $PRESS_ANY_KEY_AFTER_EACH_STEP = "Y" ]; then
    echo
    echo Press enter to continue
    read $ANY_KEY
    else
    echo
    fi
    echo "------------------------------- Import ------------------------------------"
    # create a directory for the logs
    mkdir imp_log
    # copy the env variables in the log just in case
    export > imp_log/imp_env_variable.txt
    echo "--------------------- step 1 - stop the midtier"
    # This step is needed to avoid most case of ORA-01940: user connected
    # when dropping the portal user
    $MIDTIER_ORACLE_HOME/opmn/bin/opmnctl stopall
    press_any_key
    echo "--------------------- step 2 - drop and create empty users"
    sqlplus "sys/$SYS_PASSWORD@$PORTAL_TNS as sysdba" <<IASDB
    spool imp_log/drop_create_user.log
    ---- Drop users
    -- Warning: You need to stop all SQL*Plus connection to the
    -- portal schema before that else the drop will give an
    -- ORA-01940: cannot drop a user that is currently connected
    drop user portal_public cascade;
    drop user portal_app cascade;
    drop user portal_demo cascade;
    drop user portal cascade;
    ---- Recreate the users and give them grants"
    -- The new users will have the same passwords as the users we just dropped
    -- above. Do not forget to add your exported custom users
    create user portal identified by $PORTAL_PASSWORD default tablespace portal;
    grant connect,resource,dba to portal;
    create user portal_app identified by $PORTAL_APP_PASSWORD default tablespace portal;
    grant connect,resource to portal_app;
    create user portal_demo identified by $PORTAL_DEMO_PASSWORD default tablespace portal;
    grant connect,resource to portal_demo;
    create user portal_public identified by $PORTAL_PUBLIC_PASSWORD default tablespace portal;
    grant connect,resource to portal_public;
    alter user portal_public grant connect through portal;
    start $MIDTIER_ORACLE_HOME/portal/admin/plsql/wwv/wdbigra.sql portal
    exit
    IASDB
    press_any_key
    echo "--------------------- step 3 - import"
    imp userid="'sys/$SYS_PASSWORD@$PORTAL_TNS as sysdba'" file=exp_data/portal_exp.dmp grants=y log=imp_log/import.log full=y
    press_any_key
    echo "--------------------- step 4 - import the OID users and groups (optional)"
    # Some errors will be raised when running the ldapadd because at least the
    # default entries will not be able to be inserted. Remove them from the
    # ldif file if you want to avoid them. Due to the flag '-c', ldapadd ignores
    # duplicate entries. Another more radical solution is to erase all the entries
    # of the users and groups in OID before to run the import.
    # Replace the domain name in the XML files.
    cat exp_data/portal_groups.xml | sed -e "s/$DEV_DN/$PROD_DN/" > imp_log/portal_groups.xml
    cat exp_data/portal_users.xml | sed -e "s/$DEV_DN/$PROD_DN/" > imp_log/temp_users.xml
    # Remove the authpassword attributes with a XSL stylesheet
    xml -f -s xsl/del_authpassword.xsl -o imp_log/portal_users.xml imp_log/temp_users.xml
    echo '--- Importing Groups'
    ldapadd -h $OID_HOSTNAME -p $OID_PORT -D "cn=orcladmin" -w $IAS_PASSWORD -c -X imp_log/portal_groups.xml -v
    echo '--- Importing Users'
    ldapadd -h $OID_HOSTNAME -p $OID_PORT -D "cn=orcladmin" -w $IAS_PASSWORD -c -X imp_log/portal_users.xml -v
    press_any_key
    echo "--------------------- step 5 - post import changes (SYS)"
    sqlplus "sys/$SYS_PASSWORD@$PORTAL_TNS as sysdba" <<IASDB
    spool imp_log/sys_post_changes.log
    ---- Recompile the invalid packages"
    -- On the midtier, the script utlrp is not present. This step
    -- uses a copy of it stored in patch/utlrp.sql
    select count(*) INVALID_OBJECT_BEFORE from all_objects where status='INVALID';
    start patch/utlrp.sql
    set lines 999
    select count(*) INVALID_OBJECT_AFTER from all_objects where status='INVALID';
    ---- Jobs
    -- Reassign the JOBS imported to PORTAL. After the import, they belong
    -- incorrectly to the user SYS.
    update dba_jobs set LOG_USER='PORTAL', PRIV_USER='PORTAL' where schema_user='PORTAL';
    commit;
    exit
    IASDB
    press_any_key
    echo "--------------------- step 6 - post import changes (PORTAL)"
    sqlplus $PORTAL_USER/$PORTAL_PASSWORD@$PORTAL_TNS <<IASDB
    set serveroutput on
    spool imp_log/portal_post_changes.log
    ---- Intermedia
    -- Recreate the portal indexes.
    -- inctxgrn.sql is missing from the 9040 CD-ROMS. This is the bug 3536937.
    -- Fixed in 9041. The missing script is contained in the downloadable zip file.
    start patch/inctxgrn.sql
    start $MIDTIER_ORACLE_HOME/portal/admin/plsql/wws/ctxcrind.sql
    ---- Import error
    alter table "WWSRC_PREFERENCE$" add constraint wwsrc_preference_pk
    primary key (subscriber_id, id)
    using index wwsrc_preference_idx1
    begin
    DBMS_RLS.ADD_POLICY ('', 'WWSRC_PREFERENCE$', 'WEBDB_VPD_POLICY',
    '', 'webdb_vpd_sec', 'select, insert, update, delete', TRUE,
    static_policy=>true);
    end ;
    ---- Modify tables with full URLs
    -- If the domain name of prod and dev are different, this step is really important.
    -- It modifies the portal tables that contains reference to the hostname or port
    -- of the development machine. (For more explanation: see Addional steps in the note)
    -- groups (dn)
    update wwsec_group$
    set dn=replace( dn, '$DEV_DN', '$PROD_DN' )
    update wwsec_group$
    set dn_hash = wwsec_api_private.get_dn_hash( dn )
    -- users (dn)
    update wwsec_person$
    set dn=replace( dn, '$DEV_DN', '$PROD_DN' )
    update wwsec_person$
    set dn_hash = wwsec_api_private.get_dn_hash( dn)
    -- subscriber
    update wwsub_model$
    set dn=replace( dn, '$DEV_DN', '$PROD_DN' ), GUID=':1'
    where dn like '%$DEV_DN%'
    -- preferences
    update wwpre_value$
    set varchar2_value=replace( varchar2_value, '$DEV_DN', '$PROD_DN' )
    where varchar2_value like '%$DEV_DN%'
    update wwpre_value$
    set varchar2_value=replace( varchar2_value, '$DEV_HOSTNAME:$DEV_PORT', '$PROD_HOSTNAME:$PROD_PORT' )
    where varchar2_value like '%$DEV_HOSTNAME:$DEV_PORT%'
    -- page url items
    update wwv_things
    set title_link=replace( title_link, '$DEV_HOSTNAME:$DEV_PORT', '$PROD_HOSTNAME:$PROD_PORT' )
    where title_link like '%$DEV_HOSTNAME:$DEV_PORT%'
    -- web providers
    update wwpro_providers$
    set http_url=replace( http_url, '$DEV_HOSTNAME:$DEV_PORT', '$PROD_HOSTNAME:$PROD_PORT' )
    where http_url like '%$DEV_HOSTNAME:$DEV_PORT%'
    -- html links created by the RTF editor inside text items
    update wwv_text
    set text=replace( text, '$DEV_HOSTNAME:$DEV_PORT', '$PROD_HOSTNAME:$PROD_PORT' )
    where text like '%$DEV_HOSTNAME:$DEV_PORT%'
    -- Portlet metadata nls: help URL
    update wwpro_portlet_metadata_nls$
    set help_url=replace( help_url, '$DEV_HOSTNAME:$DEV_PORT', '$PROD_HOSTNAME:$PROD_PORT' )
    where help_url like '%$DEV_HOSTNAME:$DEV_PORT%'
    -- URL items (There is a trigger on this table building absolute_url automatically)
    update wwsbr_url$
    set absolute_url=replace( absolute_url, '$DEV_HOSTNAME:$DEV_PORT', '$PROD_HOSTNAME:$PROD_PORT' )
    where absolute_url like '%$DEV_HOSTNAME:$DEV_PORT%'
    -- Things attributes
    update wwv_thingattributes
    set value=replace( value, '$DEV_HOSTNAME:$DEV_PORT', '$PROD_HOSTNAME:$PROD_PORT' )
    where value like '%$DEV_HOSTNAME:$DEV_PORT%'
    commit;
    exit
    IASDB
    press_any_key
    echo "--------------------- step 7 - ptlconfig"
    # Configure portal such that portal uses the infrastructure database
    cd $MIDTIER_ORACLE_HOME/portal/conf/
    ./ptlconfig -dad portal
    cd -
    mv $MIDTIER_ORACLE_HOME/portal/logs/ptlconfig.log imp_log
    press_any_key
    echo "--------------------- step 8 - restart the midtier"
    $MIDTIER_ORACLE_HOME/opmn/bin/opmnctl startall
    date
    Each step can generate his own errors due to a lot of factors. It is better to run the import step by step the first time.
    Do not forget to check the output of log files created during the various steps of the import:
    imp_log/drop_create_user.log
    Spool when dropping and recreating the portal users
    imp_log/import.log Import log file when importing the portal_exp.dmp file
    imp_log/sys_post_changes.log
    Spool when making post changes with SYS
    imp_log/portal_post_changes.log
    Spool when making post changes with PORTAL
    imp_log/ptlconfig.log
    Log file of ptconfig when rewiring the midtier
    Step 4 - Test
    A. Check the log files
    B. Test the website and see if it works fine.
    Step 5 - take a backup
    Take a backup of all ORACLE_HOME and DATABASES to prevent all hardware problems. You need to copy:
    All the files of the 2 ORACLE_HOME
    And all the database files.
    Step 6 - Additional steps
    Here are some additional steps.
    SSO external application ( that are part of the orasso schema and not imported yet )
    Page URL items ( they seems to store the full URL ) - included in imp_portal_schema.sh
    Web Providers ( the URL needs to be changed ) - included in imp_portal_schema.sh
    Text items edited with the RTF editor in IE and containing links - included in imp_portal_schema.sh
    Most of them are taken care by the "step 8 - post import changes". Except the first one.
    1. SSO import
    This script imports only Portal and the users/groups of OID. Not the list of the external application contained in the orasso user.
    In Portal 9.0.4, there is a script called SSOMIG that resides in $INFRA_ORACLE_HOME/sso/bin and allows to move :
    Definitions and user data for external applications
    Registration URLs and tokens for partner applications
    Connection information used by OracleAS Discoverer to access various data sources
    See:
    Oracle® Application Server Single Sign-On Administrator's Guide 10g (9.0.4) Part Number B10851-01
    14. Exporting and Importing Data
    2. Page items: the page URL items store the full URL.
    This is Bug 2661805 fixed in Portal 9.0.2.6.
    This following work-around is implemented in post import step of imp_portal_schema.sh
    -- page url items
    update wwv_things
    set title_link=replace( title_link, 'dev.dev_domain.com:7778', 'prod.prod_domain.com:7778' )
    where title_link like '%$DEV_HOSTNAME:$DEV_PORT%'
    2. Web Providers
    The URL to the Web providers needs also change. Like for the Page items, they contain the full path of the webserver.
    Or you can get the list of the URLs to change with this query
    select name, http_url from PORTAL.WWPRO_PROVIDERS$ where http_url like '%';
    This following work-around is implemented in post import step of imp_portal_schema.sh
    -- web providers
    update wwpro_providers$
    set http_url=replace( http_url, 'dev.dev_domain.com:7778', 'prod.prod_domain.com:7778' )
    where http_url like '%$DEV_HOSTNAME:$DEV_PORT%'
    4. The production and development machine do not share the same domain
    If the domain of the production and the development are not the same, the DN (name in LDAP) of all users needs to change.
    Let's say from
    dc=dev_domain,dc=com -> dc=prod_domain,dc=com
    1. before to upload the ldif files. All the strings in the 2 ldifs files that contain 'dc=dev_domain,dc=com', have to be replaced by 'dc=prod_domain,dc=com'
    2. in the wwsec_group$ and wwsec_person$ tables in portal, the DN need to change too.
    This following work-around is implemented in post import step of imp_portal_schema.sh
    -- groups (dn)
    update wwsec_group$
    set dn=replace( dn, 'dc=dev_domain,dc=com', 'dc=prod_domain,dc=com' )
    update wwsec_group$
    set dn_hash = wwsec_api_private.get_dn_hash( dn )
    -- users (dn)
    update wwsec_person$
    set dn=replace( dn, 'dc=dev_domain,dc=com', 'dc=prod_domain,dc=com' )
    update wwsec_person$
    set dn_hash = wwsec_api_private.get_dn_hash( dn)
    5. Text items with HTML links
    Sometimes people stores full URL inside their text items, it happens mostly when they use link with the RichText Editor in IE .
    This following work-around is implemented in post import step in imp_portal_schema.sh
    -- html links created by the RTF editor inside text items
    update wwv_text
    set text=replace( text, 'dev.dev_domain.com:7778', 'prod.prod_domain.com:7778' )
    where text like '%$DEV_HOSTNAME:$DEV_PORT%'
    6. OID Custom password policy
    It happens quite often that the people change the password policy of the OID server. The reason is that with the default policy, the password expires after 60 days. If so, do not forget to make the same changes in the new installation.
    PROBLEMS
    1. Import log has some errors
    A. EXP-00091 -Exporting questionable statistics
    You can ignore this error.
    B. IMP-00017 - WWSRC_PREFERENCE$
    When importing, there is one import error:
    IMP-00017: following statement failed with ORACLE error 921:
    "ALTER TABLE "WWSRC_PREFERENCE$" ADD "
    IMP-00003: ORACLE error 921 encountered
    ORA-00921: unexpected end of SQL commandThe primary key is not created. You can create it with this commmand
    in SQL*Plus with the user portal.. Then readd the missing VPD policy.
    alter table "WWSRC_PREFERENCE$" add constraint wwsrc_preference_pk
    primary key (subscriber_id, id)
    using index wwsrc_preference_idx1
    begin
    DBMS_RLS.ADD_POLICY ('', 'WWSRC_PREFERENCE$', 'WEBDB_VPD_POLICY',
    '', 'webdb_vpd_sec', 'select, insert, update, delete', TRUE,
    static_policy=>true);
    end ;
    Step 8 in the script "imp_portal_schema.sh" take care of this. This can also possibly be solved by the
    C. IMP-00017 - WWDAV$ASL
    . importing table "WWDAV$ASL"
    Note: table contains ROWID column, values may be obsolete 113 rows importedThis error is normal, the table really contains a ROWID column.
    D. IMP-00041 - Warning: object created with compilation warnings
    This error is normal too. The packages giving these error have
    dependencies on package not yet imported. A recompilation is done
    after the import.
    E. ldapadd error 'cannot add add entries containing authpasswords'
    # ldap_add: DSA is unwilling to perform
    # ldap_add: additional info: You cannot add entries containing authpasswords.
    "authpasswords" are automatically generated values from the real password of the user stored in userpassword. These values do not have to be exported from ldap.
    In the import script, I remove the additional tag with a XSL stylesheet 'del_authpassword.xsl'. See above.
    F. IMP-00017: WWSTO_SESSION$
    IMP-00017: following statement failed with ORACLE error 2298:
    "ALTER TABLE "WWSTO_SESSION$" ENABLE CONSTRAINT "WWSTO_SESS_FK1""
    IMP-00003: ORACLE error 2298 encountered
    ORA-02298: cannot validate (PORTAL.WWSTO_SESS_FK1) - parent keys not found
    Here is a work-around for the problem. I will normally integrate it in a next version of the scripts.
    SQL> delete from WWSTO_SESSION_DATA$;
    7690 rows deleted.
    SQL> delete from WWSTO_SESSION$;
    1073 rows deleted.
    SQL> commit;
    Commit complete.
    SQL> ALTER TABLE "WWSTO_SESSION$" ENABLE CONSTRAINT "WWSTO_SESS_FK1";
    Table altered.
    G. IMP-00017 - ORACLE error 1 - DBMS_JOB.ISUBMIT
    This error can appear during the import when the import database is not empty and is already customized for some reasons. For example, you export from an infrastructure and you import in a database with a lot of other programs that uses jobs. And unhappily the same job id.
    Due to the way the export/import of jobs is done, the jobs keeps their id after the import. And they may conflict.
    IMP-00017: following statement failed with ORACLE error 1: "BEGIN DBMS_JOB.ISUBMIT(JOB=>42,WHAT=>'begin execute immediate " "''begin wwutl_cache_sys.process_background_inval; end;'' ; exc" "eption when others then wwlog_api.log(p_domain=> ''utl'', " " p_subdomain=>''cache'', p_name=>''background'', " " p_action=>''process_background_inval'', p_information => ''E" "rror in process_background_inval ''|| sqlerrm);end;', NEXT_DATE=" ">TO_DATE('2004-08-19:17:32:16','YYYY-MM-DD:HH24:MI:SS'),INTERVAL=>'SYSDATE " "+ 60/(24*60)',NO_PARSE=>TRUE); END;"
    IMP-00003: ORACLE error 1 encountered ORA-00001: unique constraint (SYS.I_JOB_JOB) violated
    ORA-06512: at "SYS.DBMS_JOB", line 97 ORA-06512: at line 1
    Solutions:
    1. use a fresh installed database,
    2. Due that the jobs conflicting are different because it happens only in custom installation, there is no clear rule. But you can
    recreate the jobs lost after the import with other_ids
    and/or change the job id of the other program before to import. This type of commands can help you (you need to do it with SYS)
    select * from dba_jobs;
    update dba_jobs set job=99 where job=52;
    commit
    2. Import in a RAC environment
    Be aware of the Bug 2479882 when the portal database is in a RAC database.
    Bug 2479882 : NEEDED TO BOUNCE DB NODES AFTER INSTALLING PORTAL 9.0.2 IN RAC NODE3. Intermedia
    After importing a environment, the intermedia indexes are invalid. To correct the error you need to run in SQL*Plus with Portal
    start $MIDTIER_ORACLE_HOME/portal/admin/plsql/wws/inctxgrn.sql
    start $MIDTIER_ORACLE_HOME/portal/admin/plsql/wws/ctxcrind.sql
    But $MIDTIER_ORACLE_HOME/portal/admin/plsql/wws/inctxgrn.sql is missing in IAS 9.0.4.0. This is Bug 3536937. Fixed in 9041. The missing scripts are contained in the downloadable zip file (exp_schema904.zip : Attachment 276688.1:1 ), directory sql. This means that practically in 9040, you have to run
    start sql/inctxgrn.sql
    start $MIDTIER_ORACLE_HOME/portal/admin/plsql/wws/ctxcrind.sql
    In the import script, it is done in the step 6 - recreate Portal Intermedia indexes.
    You can not WA the problem without the scripts. Running ctxcrind.sql alone does not work. You will have this error:
    ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-06512: at "PORTAL.WWERR_API_EXCEPTION", line 164
    ORA-06512: at "PORTAL.WWV_CONTEXT", line 1035
    ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-06512: at "PORTAL.WWERR_API_EXCEPTION", line 164
    ORA-06512: at "PORTAL.WWV_CONTEXT", line 476
    ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-20000: Oracle Text error:
    DRG-12603: CTXSYS does not own user datastore procedure: WWSBR_THING_CTX_69
    ORA-06512: at line 13
    4. ptlconfig
    If you try to run ptlconfig simply after an import you will get an error:
    Problem processing Portal instance: Configuring HTTP server settings : Installing cache data : SQL exception: ERROR: ORA-23421: job number 32 is not a job in the job queue
    This is because the import done by user SYS has imported the PORTAL jobs to the SYS schema in place of portal. The solution is to run
    update dba_jobs set LOG_USER='PORTAL', PRIV_USER='PORTAL' where schema_user='PORTAL';
    In the import script, it is done in the step 8 - post import changes.
    5. WWC-41417 - invalid credentials.
    When you try to login you get:
    Unexpected error encountered in wwsec_app_priv.process_signon (User-Defined Exception) (WWC-41417)
    An exception was raised when accessing the Oracle Internet Directory: 49: Invalid credentials
    Details
    Error:Operation: dbms_ldap.simple_bind_s
    OID host: machine.domain.com
    OID port number: 4032
    Entry DN: orclApplicationCommonName=PORTAL,cn=Portal,cn=Products,cn=OracleContext. (WWC-41743)Solution:
    - run secupoid.sql
    - rerun ptlconfig
    This problem has been seen after using ptlasst in place of ptlconfig.
    6. EXP-003 with a database 9.2.0.5 or 10.1.0.2
    In fact, the DB format of imp/exp has changed in 9.2.0.5 or 10.1.0.2. The EXP-3 error only occurs when the export from the 9.2.0.5.0 or 10.1.0.2.0 database is done with a lower release export utility, e.g. 9.2.0.4.0.
    Due to the way this note is written, the imp/exp utility used is the one of the midtier (9014), if your portal resides in a 9.2.0.5 database, it will not work. To work-around the problem, there are 2 solutions:
    Change the script so that it uses the exp and imp command of database.
    Make a change to the 9.2.0.5 or 10.1.0.2 database to make them compatible with previous version. The change is to modify a database internal view before to export/import the data.
    A work-around is given in Bug 3784697
    1. Make a note of the export definition of exu9tne from
    $OH/rdbms/admin/catexp.sql
    2. Copy this to a new file and add "UNION ALL select * from sys.exu9tneb" to the end of the definition
    3. Run this as sys against the DB to be exported.
    4. Export as required
    5. Put back the original definition of exu9tne
    eg: For 9204 the workaround view would be:
    CREATE OR REPLACE VIEW exu9tne (
    tsno, fileno, blockno, length) AS
    SELECT ts#, segfile#, segblock#, length
    FROM sys.uet$
    WHERE ext# = 1
    UNION ALL
    select * from sys.exu9tneb
    7. EXP-00006: INTERNAL INCONSISTENCY ERROR
    This is Bug 2906613.
    The work-around given in this bug is the following:
    - create the following view, connected as sys, before running export:
    CREATE OR REPLACE VIEW exu8con (
    objid, owner, ownerid, tname, type, cname,
    cno, condition, condlength, enabled, defer,
    sqlver, iname) AS
    SELECT o.obj#, u.name, c.owner#, o.name,
    decode(cd.type#, 11, 7, cd.type#),
    c.name, c.con#, cd.condition, cd.condlength,
    NVL(cd.enabled, 0), NVL(cd.defer, 0),
    sv.sql_version, NVL(oi.name, '')
    FROM sys.obj$ o, sys.user$ u, sys.con$ c,
    sys.cdef$ cd, sys.exu816sqv sv, sys.obj$ oi
    WHERE u.user# = c.owner# AND
    o.obj# = cd.obj# AND
    cd.con# = c.con# AND
    cd.spare1 = sv.version# (+) AND
    cd.enabled = oi.obj# (+) AND
    NOT EXISTS (
    SELECT owner, name
    FROM sys.noexp$ ne
    WHERE ne.owner = u.name AND
    ne.name = o.name AND
    ne.obj_type = 2)
    The modification of exu8con simply adds support for a constraint type that had not previously been supported by this view. There is no negative impact.
    8. WWSBR_DOC_CTX_54 is invalid
    After the recompilation of the package, one package remains invalid (in sys_post_changes.log):
    INVALID_OBJECT_AFTER
    1
    select owner, object_name from all_objects where status='INVALID'
    CTXSYS WWSBR_DOC_CTX_54
    CREATE OR REPLACE procedure WWSBR_DOC_CTX_54
    (rid in rowid, bilob in out NOCOPY blob)
    is begin PORTAL.WWSBR_CTX_PROCS.DOC_CTX(rid,bilob);end;
    This object is not used anymore by portal. The error can be ignored. The procedure can be removed too. This is Bug 3559731.
    9. You do not have permission to perform this operation. (WWC-44131)
    It seems that there are problems if
    - groups on the production machine are not residing in the default place in OID,
    - and that the group creation base and group search base where changed.
    After this, the cloning of the repository work without problem. But it seems that the command 'ptlconfig -dad portal' does not reset the GUID and DN of the groups correctly. I have not checked this yet.
    The solution seems to use the script given in the 9.0.2 Note 228516.1. And run group_sec.sql to reset all the DN and GUID in the copied instance.
    10. Invalid Java objects when exporting from a 9.x database and importing in a 10g database
    If you export from a 9.x database and import in a 10g database, after running utlrp.sql, 18 Java objects will be invalid.
    select object_name, object_type from user_objects where status='INVALID'
    SQL> /
    OBJECT_NAME OBJECT_TYPE
    /556ab159_Handler JAVA CLASS
    /41bf3951_HttpsURLConnection JAVA CLASS
    /ce2fa28e_ProviderManagerClien JAVA CLASS
    /c5b98d35_ServiceManagerClient JAVA CLASS
    /d77cf2ab_SOAPServlet JAVA CLASS
    /649bf254_JavaProvider JAVA CLASS
    /a9164b8b_SpProvider JAVA CLASS
    /2ee43ac9_StatefulEJBProvider JAVA CLASS
    /ad45acec_StatelessEJBProvider JAVA CLASS
    /da1c4a59_EntityEJBProvider JAVA CLASS
    /66fdac3e_OracleSOAPHTTPConnec JAVA CLASS
    /939c36f5_OracleSOAPHTTPConnec JAVA CLASS
    org/apache/soap/rpc/Call JAVA CLASS
    org/apache/soap/rpc/RPCMessage JAVA CLASS
    org/apache/soap/rpc/Response JAVA CLASS
    /198a7089_Message JAVA CLASS
    /2cffd799_ProviderGroupUtils JAVA CLASS
    /32ebb779_ProviderGroupMgrProx JAVA CLASS
    18 rows selected.
    This is a known issue. This can be solved by applying patch one of the following patch depending of your IAS version.
    Bug 3405173 - PORTAL 9.0.4.0.0 PATCH FOR 10G DB UPGRADE (FROM 9.0.X AND 9.2.X)
    Bug 4100409 - PORTAL 9.0.4.1.0 PATCH FOR 10G DB UPGRADE (FROM 9.0.X AND 9.2.X)
    Bug 4100417 - PORTAL 9.0.4.2.0 PATCH FOR 10G DB UPGRADE (FROM 9.0.X AND 9.2.X)
    11. Import : IMP-00003: ORACLE error 30510 encountered
    When importing Portal 9.0.4.x, it could be that the import of the database side produces an error ORA-30510.The new perl script work-around the issue in the portal_post_import.sql script. But not the BASH scripts. If you use the BASH scripts, after the import, please run this command manually in SQL*Plus logged as portal.
    ---- Import error 2 - ORA-30510 when importing
    CREATE OR REPLACE TRIGGER logoff_trigger
    before logoff on schema
    begin
    -- Call wwsec_oid.unbind to close open OID connections if any.
    wwsec_oid.unbind;
    exception
    when others then
    -- Ignore all the errors encountered while unbinding.
    null;
    end logoff_trigger;
    This is logged as <Bug;4458413>.
    12. Exporting from a 9.0.1 database and import in a 9.2.0.5+ or 10g DB
    It could be that when exporting from a 9.0.1 database to a 10g database that the java classes do not get compiled correctly. The following errors are seen
    ORA-29534: referenced object PORTAL.oracle/net/www/proto/https/HttpsURLConnection could not be resolved
    errors:: class oracle/net/www/proto/https/HttpsURLConnection
    ORA-29521: referenced name oracle/security/ssl/OracleSSLSocketFactoryImpl could not be found
    ORA-29521: referenced name oracle/security/ssl/OracleSSLSocketFactory could not be found
    In such a case, please apply the following patches after the import in the 10g database.
    Bug 3405173 PORTAL REPOS DB UPGRADE TO 10G: for Portal 9.0.4.0
    Bug 4100409 PORTAL REPOS DB UPGRADE TO 10G: for Portal 9.0.4.1
    Main Differences with Portal 9.0.2
    For the persons used to this technics in Portal 9.0.2, you could be interested to read the main differences with the same note for Portal 9.0.2
    Portal 9.0.2
    Portal 9.0.4
    Cutter database
    Portal 9.0.2 can be part of an infrastructure database or in a custom external database.
    In Portal 9.0.2, the portal schema is imported in an empty database.
    Portal 9.0.4 can only be installed in a 'Cutter database', a database created with RepCA or OUI containing always OID, DCM and so on...
    In Portal 9.0.4, the portal schema is imported in an 'Cutter database' (new)
    group_sec.sql
    group_sec.sql is used to correct the GUIDs of OID stored in Portal
    ptlconfig -dad portal -oid is used to correct the GUIDs of OID stored in Portal (new)
    1 script
    The import / export are divided by several steps with several scripts
    The import script is done in one step
    Additional steps are included in the script
    This requires to know the hostname and port of the original development machine. (new)
    Import
    The steps are:
    creation of an empty database
    creation of the users with password=username
    import
    The steps are:
    creation of an IAS 10g infrastructure DB (repca or OUI)
    deletion of new portal schemas (new)
    creation of the users with the same password than the schemas just dropped.
    import
    DAD
    The dad needed to be changed
    The passwords are not changed, the dad does not need to be changed.
    Bugs
    In portal 9.0.2, 2 bugs were workarounded by change_host.sh
    In Portal 9.0.4, some tables additional tables needs to be updated manually before to run ptlasst. This is #Bug:3762961#.
    export of LDAP
    The export is done in LDIF files. If the prod and the dev have different domain, it is quite difficult to change the domain name in these file due to the line wrapping at 78 characters.
    The export is done in XML files, in the DSML format (new). It is a lot easier to change the XML files if the domain name is different from PROD to DEV.
    Download
    You have to cut and paste the scripts
    The scripts are attached to the note. Just donwload them.
    Rewiring
    9.0.2 uses ptlasst.
    ptlasst.csh -mode MIDTIER -i custom -s $PORTAL_USER -sp $PORTAL_PASSWORD -c $PORTAL_HOSTNAME:$PORTAL_DB_PORT:$PORTAL_SERVICE_NAME -sdad $PORTAL_DAD -o orasso -op $ORASSO_PASSWORD -odad orasso -host $MIDTIER_HOSTNAME -port $MIDTIER_HTTP_PORT -ldap_h $INFRA_HOSTNAME -ldap_p $OID_PORT -ldap_w $IAS_PASSWORD -pwd $IAS_PASSWORD -sso_c $INFRA_HOSTNAME:$INFRA_DB_PORT:$INFRA_SERVICE_NAME -sso_h $INFRA_HOSTNAME -sso_p $INFRA_HTTP_PORT -ultrasearch -oh $MIDTIER_ORACLE_HOME -mc false -mi true -chost $MIDTIER_HOSTNAME -cport_i $WEBCACHE_INV_PORT -cport_a $WEBCACHE_ADM_PORT -wc_i_pwd $IAS_PASSWORD -emhost $INFRA_HOSTNAME -emport $EM_PORT -pa orasso_pa -pap $ORASSO_PA_PASSWORD -ps orasso_ps -pp $ORASSO_PS_PASSWORD -iasname $IAS_NAME -verbose -portal_only
    9.0.4 uses ptlconfig (new)
    ptlconfig -dad portal
    Environment variables
    A lot of environment variables are needed
    Just 3 environment variables are needed:
    - password of SYS
    - password of IAS,
    - ORACLE_HOME of the Midtier
    All the rest is found in iasconfig.xml and LDAP (new)
    TO DO
    - Check if the orclcommonapplication name fits SID.hostname
    - Check what gives the import of a portal30 upgraded schema inside a schema named portal
    - Explain how to copy the portal*.dbf files in place of export/import and the limitation of tra

  • GeoRaster in the Enterprise - tips?

    Next week I will start a pilot project loading mid to high resolution (0.5M to 0.1M) orthophotos for about 200 sites around 13000 hectares (50 Sq Mi) each. The sites are for the most part not contiguous, but the data is global. The source format is mostly MrSID, although for about 20% of the sites, Tiff or PNG formats are available, with a few ecw's as well. I plan to unproject and store the photo data in 8307 (lat/lon) format, as that is what our application uses for our native format, and to allow global coverage.
    The data will be used in three ways:
    First, it will be retrieved in defined tile sizes and scales for a home-gown Java rich-client application so that tiles can be saved to the client's disk to minimize repetitive bandwidth requirements. For areas not covered by these orthos, MS VE tiles will be used.
    Second, it will be exposed for others to use as a WMS service.
    Third, as a source for "export" into other formats on an on-demand process.
    We are using 64-bit Oracle 10gR2 on Solaris x86 with NetApp filers on the db end, and 64-bit Windows servers on the app end, all on a GBE network. I have both FME 2007 and Manifold v8 available for data conversion functions. For data serving, GeoServer and FME (for option three) are planned as we already use GeoServer successfully for WFS duties.
    I am looking for suggestions / tips from anyone on how best to load and store the imagery, and then optimize the retrieval of it. I've read the GeoRaster user guide (and starting reading the 11g one) and the book.
    I am particularity interested in what to do when you do have overlapping images (two sites that overlap). Also, how to best load a site when the site is not one image, but made up of tiles.
    For software, say, if Mapviewer has proven faster for WMS than GeoServer for you, I'm willing to listen.
    Thanks in advance,
    Bryan

    1. yes, (256,256,1) or (256,256,3) shall work fine. in this case, your focus is on displaying or retrieval, it's better to make sure (1) the images are stored using the same block size, ie, (256,256,1) or (256,256,3) and (2) when you retrieve the tiles control your query window to cover exactly the area of the tiles (ie, avoiding internal mosaicking and cropping).
    2. yes, in a regular tablespace, if you have a LOT of image data and concurrent multi-users, the more data files the better. you can make tens of them. when dealing with geoimages, ten data files is probably minimum. but you might also want to consider Oracle BIG TABLESPACE, in which only one data file (could be in terabytes) is allowed. we didn't do much tests on it. but seems the performance is very good.
    3. i think it all depends. seems your major purpose is to quickly retrieve and display the images, pan thru and zoom in/out smoothly across many images and around the globe. if so, i agree you'd better do some preprocessing so that the data have the same resolution and pyramids. to do this, scaleCopy can be considered.
    hope this helps a bit.
    jeffrey

  • Warning Messages when starting Application

    Hello,
    I get those messages when starting my application:
    WARN - [ConverterRule]{faces-config/converter} Merge(null,java.math.BigDecimal)
    WARN - [ConverterRule]{faces-config/converter} Merge(null,java.math.BigInteger)
    WARN - [ManagedBeanRule]{faces-config/managed-bean} Merge(Login)
    WARN - [NavigationRuleRule]{faces-config/navigation-rule} Merge(/home_new.jsp)
    WARN - [NavigationRuleRule]{faces-config/navigation-rule} Merge(/records/index.jsp)
    WARN - [NavigationRuleRule]{faces-config/navigation-rule} Merge(/admin/*)
    WARN - [NavigationRuleRule]{faces-config/navigation-rule} Merge(*)
    WARN - [ManagedBeanRule]{faces-config/managed-bean} Merge(Record)
    WARN - [ManagedBeanRule]{faces-config/managed-bean} Merge(User)
    WARN - [ManagedBeanRule]{faces-config/managed-bean} Merge(conLayout)
    WARN - [ManagedBeanRule]{faces-config/managed-bean} Merge(UserMgr)
    WARN - [ManagedBeanRule]{faces-config/managed-bean} Merge(AdmMgr)
    WARN - [ComponentRule]{faces-config/component} Merge(MessageImg)
    Should I do something to avoid those messages?
    Thanks
    Rene

    JSF sees and merges all configuration files listed below:
    (1) WEB-INF/faces-config.xml
    (2) some xml files you specify using the context-param element of WEB-INF/web.xml
    (3) META-INF/faces-config.xml files included in all jar files
    Check the all configuration files and see whether they have doubled elements
    and merge them.

  • User authentication against LDAP - Non-AD

    Hi,
    We are trying to setup LDAP authentication against an LDAP, Oracle Unified Directory and below are the parameters of ldap.properties file:
    ldapAuthentication.defaultRole = ROLE_AUTHENTICATED_PRINCIPAL
    ldapAuthentication.enabled = true
    ldapAuthentication.tryNextProviderIfNoAuthenticated = true
    ldapAuthentication.stopIfCommunicationError = true
    ldapAuthentication.url=ldap\://localhost:389/
    ldapAuthentication.rootContext=DC=test,DC=com
    ldapAuthentication.securityPrincipal=CN=Directory Manager
    ldapAuthentication.securityCredential.encrypted=password
    ldapAuthentication.keepContextPrefix=false
    ldapAuthentication.isAD=false
    ldapAuthentication.userAccountSearchKey=CN
    ldapAuthentication.firstNameSearchKey=givenName
    ldapAuthentication.lastNameSearchKey=sn
    Still I am getting while I try to login to OIA as an OUD user:
    WARN [UserManagerImpl] RbacxUser with username: 'cn=oiaadmin' not found
    Please help

    Hi Jcorker,
    According to your description, you need to access the SQL Serve Analysis Services database which is configured as cluster for SQL & SSAS from another domain, right?
    In SSAS we can use the solution below achieve the requirement.
    1.Create new domain account and impersonate the web site with that.
    2.Create local user account on the analysis service with same exact username/password as like domain account created in the previous step.
    However, you cannot create a local account with the same name on both servers. I have tested it on my local environemnt, we can create the same local account with the same name on both servers. In your scenario, if DB1 and DB2 on different server, you can
    create a local account with the same name on both servers. Please post the detail errors, so that we can make further analysis.
    Besides, SSAS only allows users of the same domain or trusted domains and it does not allow users from any domain except from these two. You can configure the trust relationship between the domains.
    http://technet.microsoft.com/en-us/library/cc961481.aspx
    Regards,
    Charlie Liao
    If you have any feedback on our support, please click
    here.
    Charlie Liao
    TechNet Community Support

  • WARNING UNITY SERVER

    Hi,
    I have the next warning of the Unity server:
    Level Computer Log Date and Time Source Category Event User 
    Warning SVR-UNY-02 Application 2/7/2012 8:43:01 AM CiscoUnity_ConvSub  1053  
    While running the subscriber conversation for user:(MARIA JULIAN ESQUIVIAS) 
    with extension:(1063) an error occurred when trying to match the message sender 
    (AVP_SENDER_OBJECT_ID) to a subscriber in the Unity database. The following 
    error was returned:(HR [IAvDohMessage::get_Sender]). 
    The subscriber conversation treated the message as if it was from an unknown 
    subscriber. As a result the subscriber's recorded name, if available, was not 
    played back and reply options were not available. 
    Please run DBWalker from Cisco Unity Tools Depot with the option 'Check for 
    orphaned entries in the GlobalSubscriber table' to check for database 
    inconsistencies.
    Level Computer Log Date and Time Source Category Event User 
    Warning SVR-UNY-02 Application 2/7/2012 8:43:01 AM CiscoUnity_ConvSub  1053  
    While running the subscriber conversation for user:(MARIA JULIAN ESQUIVIAS) 
    with extension:(1063) an error occurred when trying to match the message sender 
    (AVP_SENDER_OBJECT_ID) to a subscriber in the Unity database. The following 
    error was returned:(HR [IAvDohMessage::get_Sender]). 
    The subscriber conversation treated the message as if it was from an unknown 
    subscriber. As a result the subscriber's recorded name, if available, was not 
    played back and reply options were not available. 
    Please run DBWalker from Cisco Unity Tools Depot with the option 'Check for 
    orphaned entries in the GlobalSubscriber table' to check for database 
    inconsistencies.
    =====================================================================
    The customer wants to know, Why is this warning?
    Thanks for your help,
    Regards,
    David

    Here is a similar post that has some follow-up:
    https://supportforums.cisco.com/thread/312506

  • CAML query to return multi-user field from a Sharepoint list

    I have a list in SharePoint that contains a field of type Multi-User which can contain 1 to many user names. I'm having trouble returning a string containing anything when more then 1 user is selected in the field.  Can someone point me in the right
    direction?

    You can't query on a Mutli-user field using a "contains" filter - using the GUI. 
    However, you can change the CAML for the query using SharePoint Designer.
    E.g. In my view, I want to return a list of documents where the Contributor field (a multi-user field) contains the user "Warner".
    In the GUI, I create the view, but I'm not allowed to use the filter "Contains", so I use "Equals" instead. Of this won't work unless the only user is "Warner". So I open SharePoint Designer, and I change the query used on that view from Eq to Contains.
    Original query:
    <View Name="{D0E65C04-0A53-4C26-9004-68B3CFF1F11A}" MobileView="TRUE" Type="HTML" DisplayName="Warners Documents" Url="/Shared Documents/Forms/Warners Documents.aspx" Level="1" BaseViewID="1" ContentTypeID="0x" ImageUrl="/_layouts/15/images/dlicon.png?rev=23" >
    <Query>
    <Where>
    <Eq>
    <FieldRef Name="Contributors"/>
    <Value Type="Text">Warner</Value>
    </Eq>
    </Where>
    </Query>
    <ViewFields>
    <FieldRef Name="DocIcon"/>
    <FieldRef Name="LinkFilename"/>
    <FieldRef Name="Modified"/>
    <FieldRef Name="Editor"/>
    <FieldRef Name="Contributors"/>
    </ViewFields>
    <RowLimit Paged="TRUE">30</RowLimit>
    <Aggregations Value="Off"/>
    <JSLink>clienttemplates.js</JSLink>
    <XslLink Default="TRUE">main.xsl</XslLink>
    <Toolbar Type="Standard"/>
    </View>
    New Query:
    <View Name="{D0E65C04-0A53-4C26-9004-68B3CFF1F11A}" MobileView="TRUE" Type="HTML" DisplayName="Warners Documents" Url="/Shared Documents/Forms/Warners Documents.aspx" Level="1" BaseViewID="1" ContentTypeID="0x" ImageUrl="/_layouts/15/images/dlicon.png?rev=23" >
    <Query>
    <Where>
    <Contains>
    <FieldRef Name="Contributors"/>
    <Value Type="Text">Warner</Value>
    </Contains>
    </Where>
    </Query>
    <ViewFields>
    <FieldRef Name="DocIcon"/>
    <FieldRef Name="LinkFilename"/>
    <FieldRef Name="Modified"/>
    <FieldRef Name="Editor"/>
    <FieldRef Name="Contributors"/>
    </ViewFields>
    <RowLimit Paged="TRUE">30</RowLimit>
    <Aggregations Value="Off"/>
    <JSLink>clienttemplates.js</JSLink>
    <XslLink Default="TRUE">main.xsl</XslLink>
    <Toolbar Type="Standard"/>
    </View>
    This now works.
    However, the SharePoint team probably put this restriction in place for a reason. Possibly a performance related reason, due to the query performed on the SQL server, so use this method with caution.
    Regards, Matthew
    MCPD | MCITP
    My Blog
    View
    Matthew Yarlett's profile
    See my webpart on the TechNet Gallery that allows administrative users to upload, crop and format user profile photos. Check it out here:
    Upload and Crop User Profile Photos

  • [10G] DATAPUMP IMPORT는 자동으로 USER 생성

    제품 : ORACLE SERVER
    작성날짜 : 2004-05-28
    [10G] DATAPUMP IMPORT는 자동으로 USER 생성
    ===================================
    PURPOSE
    다음은 DATAPUMP의 기능을 소개하고자 한다.
    Explanation
    imp utility 에서는 target user가 존재해야 했었다
    그러나 DATAPUMP 는 만익 target user가 존재하지 않는다면
    이를 자동으로 생성한다.
    Example :
    =============
    Source database 에서 TEST라는 user 가 있다.
    TEST ( password : test , role : connect , resource )
    Export the TEST schema using datapump:
    expdp system/oracle dumpfile=exp.dmp schemas=TEST
    Case I
    =======
    test user가 존재하지 않을 경우에 import 는 test user를 자동으로 생성한다.
    impdp system/oracle dumpfile=exp.dmp
    *************TEST does not exist*************************************
    Import: Release 10.1.0.2.0 - Production on Friday, 28 May, 2004 1:02
    Copyright (c) 2003, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Produc
    tion
    With the Data Mining option
    Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
    Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** dumpfile=exp.dmp
    Processing object type SCHEMA_EXPORT/USER
    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
    Processing object type SCHEMA_EXPORT/ROLE_GRANT
    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
    Processing object type SCHEMA_EXPORT/SE_PRE_SCHEMA_PROCOBJACT/PROCACT_SCHEMA
    Processing object type SCHEMA_EXPORT/DB_LINK
    Processing object type SCHEMA_EXPORT/TABLE/TABLE
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    . . imported "TEST"."DEPT" 5.648 KB 4 rows
    . . imported "TEST"."SALGRADE" 5.648 KB 10 rows
    . . imported "TEST"."BONUS" 0 KB 0 rows
    . . imported "TEST"."EMP" 0 KB 0 rows
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
    Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
    Job "SYSTEM"."SYS_IMPORT_FULL_01" successfully completed at 01:02
    connect TEST/TEST (on target database)
    => connected
    SQL> select * from session_roles;
    ROLE
    connect
    resource
    Case II
    ========
    Target database 에 TEST user가 존재하는 경우에 warning message가 발생하며 import
    작업은 계속 진행된다.
    impdp system/oracle dumpfile=exp.dmp
    *************user TEST already exists************************************
    Import: Release 10.1.0.2.0 - Production on Friday, 28 May, 2004 1:06
    Copyright (c) 2003, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Produc
    tion
    With the Data Mining option
    Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
    Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** dumpfile=exp.dmp
    Processing object type SCHEMA_EXPORT/USER
    ORA-31684: Object type USER:"TEST" already exists
    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
    Processing object type SCHEMA_EXPORT/ROLE_GRANT
    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
    Processing object type SCHEMA_EXPORT/SE_PRE_SCHEMA_PROCOBJACT/PROCACT_SCHEMA
    Processing object type SCHEMA_EXPORT/DB_LINK
    Processing object type SCHEMA_EXPORT/TABLE/TABLE
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    . . imported "TEST"."DEPT" 5.648 KB 4 rows
    . . imported "TEST"."SALGRADE" 5.648 KB 10 rows
    . . imported "TEST"."BONUS" 0 KB 0 rows
    . . imported "TEST"."EMP" 0 KB 0 rows
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
    Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
    Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 1 error(s) at 01:06
    You will receive ORA-31684 error but import will continue.
    Case - III
    ===========
    Target database에 TEST user가 존재하지만 warning (ora-31684) 을 피하기 위해서는
    EXCLUDE=USER 를 사용한다.
    impdp system/oracle dumpfile=exp.dmp exclude=user
    *********Disable create user statment as user TEST already exist***********
    Import: Release 10.1.0.2.0 - Production on Friday, 28 May, 2004 1:11
    Copyright (c) 2003, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Produc
    tion
    With the Data Mining option
    Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
    Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** dumpfile=exp.dmp exclud
    e=user
    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
    Processing object type SCHEMA_EXPORT/ROLE_GRANT
    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
    Processing object type SCHEMA_EXPORT/SE_PRE_SCHEMA_PROCOBJACT/PROCACT_SCHEMA
    Processing object type SCHEMA_EXPORT/DB_LINK
    Processing object type SCHEMA_EXPORT/TABLE/TABLE
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    . . imported "TEST"."DEPT" 5.648 KB 4 rows
    . . imported "TEST"."SALGRADE" 5.648 KB 10 rows
    . . imported "TEST"."BONUS" 0 KB 0 rows
    . . imported "TEST"."EMP" 0 KB 0 rows
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
    Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
    Job "SYSTEM"."SYS_IMPORT_FULL_01" successfully completed at 01:11
    TEST user가 존재하지 않는데 EXCLUDE=USER parameter 를 사용하면
    ORA-01917 error 를 만나게 된다.
    Reference Documents :
    Note : 272132.1 DATAPUMP import automatically creates schema

  • LDAP + DNS + noob=Massive Pain (LONG)

    I am running 10.4.11 as a home server/gateway. There are two NIC's. The first is connected directly to the modem via ethernet, the second goes to a switch for the LAN. When I set up this server I started small with AFP,DHCP, DNS, Firewall, and Web. I pointed my domain to my ip. Set up the DNS, for this example let's call the domain I am hosting homepages.com. I called the server ns1.homepages.com. I used AFP to mount the directory for the apache root and started to drop my html/php in there. Then i started up mySQL installed phpMyAdmin. Things worked. Upgraded to php5. This was frustrating but in the end, all went well. Then I added a second domain in the DNS. I selected the IP of the second NIC for this second domain because I wanted to name the computers here in my home office as i have a couple of part time employees and thought that names would be easier than IP addresses. I called the server server.home.art, with home.art being the domain. Other computers obviously had names like scanner.home.art or filemaker.home.art or entertainment.home.art, you get the idea. Now it has become rather cumbersome to manage the part time folks all on separate machines, all with local users and all with permission issues to deal with. So I started to ask around and I was told that the Open Directory service could help out. So I promoted the server to Master and immediately ran into problems. You can see a thread over at afp548 here:
    http://www.afp548.com/forum/viewtopic.php?showtopic=19082
    I guess my biggest problem here is my internal vs. external domain. When I originally promoted this to Master the Kerbos Realm and Search base were crazy, they were being pulled from the IN.ARPA from my ISP. That didn't work because the client machines couldn't resolve that, they were looking for the internal domain, home.art. It took me quite awhile to figure that out. So after many, many, many promotions/demotions of the Open Directory and many uses of changeip I am still getting errors. Either when I try and promote the server to Master or from clients. The clients range from network users being shook off with no errors to the error that started the above thread, "home directory is on an AFP volume and cannot be mounted."
    I was finally able to get my hostnames to agree with the external name, the ns1.homepages.com but then I have massive problems with the clients on the LAN connecting to the server. I REALLY want to use the Kerberos Realm: HOME.ART but it really doesn't like that. When I promote it that way it hangs when, gives me errors both in the GUI and in the logs. If I use the NS1.HOMEPAGES.COM, everything starts smoothly but then the clients have problems.
    Is there anyway to get the DNS for the internal to the Keberos Realm instead of the external? I have tried to demote the server to stand alone, save and restart. Then use "sudo changeip - myip myip ns1.homepages.com server.home.art". And then restart the machine. Premote it Master but the Keberos Realm still shows as NS1.HOMEPAGES.COM. The seach base changes to dc=server, dc=home, dc=art, But when I input a Password and "Create" the master I get an "service encountered an error" and "settings is not available, this is a one time alert" and then multiple errors in the logs, namely slapconfig:
    Creating Kerberos directory
    Creating KDC Config File
    Creating Admin ACL File
    Creating Kerberos Master Key
    Creating Kerberos Database
    Creating Kerberos Admin user
    WARNING: no policy specified for [email protected]; defaulting to no policy
    Adding kerberos auth authority to admin user
    Finally, when I demote the server, changeip the name back to the ns1 name and promote the server back AND still can't login into accounts I get errors like this in kadmin:
    Jan 13 20:36:48 ns1.homepages.com kadmin.local[1575](info): No dictionary file specified, continuing without one.
    This error hits the log in three every 4 minutes.
    Or in LDAP Log I see errors like this:
    Jan 13 20:32:23 ns1 slapd[580]: Entry (uid=hollbo,cn=users,dc=ns1,dc=homepages,dc=com): object class 'posixAccount' requires attribute 'homeDirectory'\n
    Jan 13 20:32:23 ns1 slapd[580]: entry failed schema check: object class 'posixAccount' requires attribute 'homeDirectory'\n
    Jan 13 20:36:50 ns1 slapd[580]: SASL [conn=112] Failure: no user in database\n
    Jan 13 20:37:01 ns1 slapd[580]: SASL [conn=126] Failure: no user in database\n
    Jan 13 20:39:24 ns1 slapd[580]: SASL [conn=139] Failure: no user in database\n
    Jan 13 20:41:14 ns1 slapd[580]: SASL [conn=160] Failure: no user in database\n
    Jan 13 20:42:46 ns1 slapd[580]: SASL [conn=172] Failure: no user in database\n
    Jan 13 21:11:38 ns1 slapd[580]: slapd shutdown: waiting for 0 threads to terminate\n
    Jan 13 21:11:38 ns1 slapd[580]: bdb(dc=ns1,dc=homepages,dc=com): Locker still has locks\n
    Jan 13 21:11:38 ns1 slapd[580]: bdblocker_idfree: 16 err Invalid argument(22)\n
    Jan 13 21:11:38 ns1 slapd[580]: bdb(dc=ns1,dc=homepages,dc=com): apple-category.bdb: unable to flush: No such file or directory\n
    I'm really confused and have recieved so many errors that I am beginning to wonder if I have fiddled so much that I have created serious problems with Kerberos. I don't know whether that is possible or not but I could really use some advice on this.
    thanks

    Ok Let me try this again. (My butterfingers have caused more problems with my server configuration than I can tell you).
    *The nightmare that can be Open Directory:*
    It is often best to just start over with a clean install of the server software when your OD keeps failing as you describe. This is no fun, and is time consuming, but it is more likely to give you success. (Hopefully you are paid by the hour and your boss is supportive). If you choose this route, make sure you take the following steps. During the "setup assistant" process, make the server a stand-alone server at first and *do not turn on any other services*.
    Once your server is up and running, set up your DNS configuration. DNS *absolutely must be configured correctly and queries for your OD by domain name should resolve to the machine.* If DNS isn't working, OD won't work. And you *cannot use the bonjour zeroconf/mDNS* with OD.
    The DNS zones must
    *allow recursion*
    *should not allow zone transfers*.
    Your DNS servers field in the network configuration system preference pane should point to the internal LAN DNS server IP address (If you are using DNS on the same machine as your OD, then point it to that machine's private IP address).
    Start DNS
    Restart the computer.
    With OS X 10.4 and higher, setting up your zones is much easier and less prone to error than earlier versions, but verification is important.
    Once you are rebooted, there are a number of tools you can use to test the DNS configuration.
    Check your zone files by opening terminal and typing (in your case) *sudo named-checkzone art /var/named/art.zone* or *sudo named-checkzone home.art /var/named/home.art.zone* . As you can see, the zone file is named whatever you called your zone name with the ".zone" on the end. You next need to verify that the configuration file is correct for dns. Do this by typing *sudo named-checkconf /etc/named.conf*
    Use Network Utility to perform a lookup on your server's domain name and a reverse lookup by typing in your server's IP address. If both come back without errors and look similar to a lookup of a public nameserver that you know is functional.
    Do a search here or on the web in general regarding the errors you may receive if any from these commands. Mac OS X server 10.4 uses BIND9, so the number of sites with tutorials and information about errors and configuration issues are vast.
    It is valuable to know that the location of the zone files and configuration files vary somewhat depending on the version of Linux/Unix. For instance, Debian installs put the entire batch of files in /etc/bind and separates the named.conf file from the local configuration (named.conf.local) and options named.conf.options and splits up the zone files for the localhost into groupings based on IP address octets) while Mac OS X puts the configuration files in /etc/named.conf, /etc/rndc.key, and puts the zone files in /var/named/ Regardless, the content of these files completely compatible.)
    Then you can convert the server to an open directory master. If the dialog shows the correct info for your server (DC=HOME,DC=ART) you should be good to go.
    To reiterate: if DNS is configured correctly, OD should also work properly, especially if you start with a virgin server.
    *Throwing Caution to the Wind*
    Reinstalling everything from scratch is going to result in the most durable solution. With that in mind, why not take some time to learn a bit about how the system is laid out by really mucking it up. If you are methodical enough, you may actually solve your problem in the process.
    OD stores files in certain locations in the /private/var/db/openldap and /private/etc/openldap folders. In /private/etc/openldap there are loose files in the root and a folder called schemas. The latter folder should remain unchanged from first install. It just contains the descriptors for various configurations. The files "ldap.conf and ldap.conf.default" should be relatively untouched. The slapd.conf and slapd-related files are what contain the info you need. Specifically the slapd_macosxserver.conf file. This is the only file that should contain information specific to your Open Directory configuration.
    The OD database is stored in /var/db/openldap
    Your kerberos information is stored in a number of files including /etc/krb5.keytab and /var/krb5kdc. Also information is stored in the kerberos.mit files in your /Library/Preferences folder.
    I won't tell you what to do with these files. But if you demote your server to standalone, reboot in single user mode (hold the command-s at startup, and follow the instructions to /sbin/fsck -fy and /sbin/mount -rw / at the command prompt) and move (mv) any of the files to backup folders ore rename folders so the software does not find them (except /etc/openldap/ldap.conf, ldap.conf.default, and schemas). You use the mv command to do this. mv allows you to move and rename files. It does not create new folders, so you need to do that ahead of time using mkdir if that is your plan of attack. The format of the command is fairly straightforward: if you wanted to rename the folder /var/db/openldap to a backup name you would type *mv /var/db/openldap /var/db/openldap.backup* . To move all the files within a given folder without moving the enclosing folder itself (say /tmp/501) to a new one (say /Users/administrator/Desktop/tmpBackup), you would type *mkdir /Users/administrator/Desktop/tmpBackup; mv /tmp/501/* /Users/administrator/Desktop/tmpBackup* The semi-colon tells the shell that you are starting a new command.
    Beyond this, you will have to just experiment. If anything, the half-hour you spend mucking up your system will be an invaluable learning experience even if you end up having to reinstall the OS and Server software from scratch).
    I hope this is helpful for you.

  • Lenovo Community Participat​ion Rules

    Objectives of Lenovo Discussion Forums:
    These communities have been created to provide a high quality atmosphere in which users of Lenovo products and services may share experiences and expertise. While members from Lenovo may participate at intervals to engage in the discussions and offer advice and suggestions, this forum is not designed as a dedicated and staffed support channel. This is an informal and public forum, and Lenovo does not guarantee the accuracy of information and advice posted here -- see important Warranty information below.
    RULES OF CONDUCT -- YOUR RESPONSIBILITIES
    Lenovo reserves the right to remove inappropriate language and postings, such as those examples listed below, from the discussion forums. In such instances, the user will be warned and may be banned from future participation
    Prohibitions
    No posts, forum IDs or email addresses shall contain profanity (implied or otherwise), or hate language targeting race / ethnicity, religion, gender, nationality, or political beliefs.
    Post should avoid these topics. Posts violating these rules will be moderated, and the user warned. Repeat occurrences could result in banning.
    No pornography, in the form of written words, expressions, posted images, or links to external material will be tolerated.
    No personal threats will be tolerated against forum members, Lenovo employees, or company affiliates.
    No personal attacks.
    It is fair to state disagreement with facts or conclusions that another member has posted, but dissent must be expressed in an objective, and reasoned manner. Treat others with the respect you wish to receive. Remember that the community is here to share collective experiences and wisdom, with the goal of all members enjoying greater success with their Lenovo products. Consider whether your comments serve to advance the discussion in a positive direction.
    No Trolling or deliberate disruption of discussion . Inflammatory post or thread titles are unacceptable and may be moderated.
    Inflammatory, or unnecessarily argumentative postings will be considered trolling. Extended debate with moderators or admins over their decisions with regard to moderation of posts is considered trolling. Do not subvert threads. No vendetta posts, or online campaigning. It is acceptable to state concern for how a particular Lenovo policy, performance, or procedure does or does not meet the expectation of a particular member, but it is not acceptable to use this forum in an attempt to broadly organize or incite members en mass, to cancel orders, return systems, undertake legal action or otherwise disrupt the normal business processes of Lenovo.
    No posting of private information.
    Privacy - Lenovo respects the privacy of each member - please find the privacy link in the footer on each page of the forum. As such, we request that participants respect the privacy of all community members and of Lenovo employees that they speak with on the phone, or correspond with via email. Posts revealing items such as full names, email, or direct phone numbers  of others without their express consent is prohibited.
    No commercial solicitation, other than advertisements placed by Lenovo.
    This is not intended as an online shopping or trading forum. Members may not post inventories of items, or list items for sale on a routine basis. "Wanted" posts (e.g., a member seeking a 701c system) are permitted on a one-off basis. Individuals may also post single Lenovo products, or directly related accessory items as "for sale" in the general discussion area. Posts for non Lenovo related products are not acceptable (so no cars, boats,planes, tennis rackets,MP3 players, for example). Discretion of forum administrators to remove an item is reserved in all instances.
    No solicitation for, nor exchange of information that will aid or enable unethical, illegal, immoral or unsafe activities.
    For example, no posts concerning exchange of passwords, credit or banking information, warranty entitlement information for purpose of re-entitling out of warranty products. No posts shall include instructions or directions intended to subvert security measures, including passwords, locking mechanisms, fingerprint scans, etc, or to subvert safety measures. Nor shall any posts provide descriptions to the location of, nor direct links to content related to these topics.
    Members are restricted to a single online persona
    Members may not register under multiple IDs, or utilize multiple email addresses within the Lenovo communities. This rule applies to Lenovo blogs and the forum. Posting under multiple IDs can be a deceptive practice and could create false impressions. The consistent use of a single ID / Persona whether posting response comments on Lenovo Blogs, or in active forum participation enhances the reputation and recognition of the individual community member.
    Do not embed large photos (above 100K) or cut and paste large areas (use of quote) unnecessarily as these behaviors degrade the performance of the forum and detract from the overall usability and experience of others. Instead, host photos externally and link to them as needed within your posts. If you must post to the forum, post in the photos area, remembering to title the thread  photo thread appropriately when you post them to. Try to limit each photo to 100K or less in size, and provide a warning of "large attachments" if you are posting lots of pictures or if you had to go above 100K.
    You can check out this article About Posting Pictures In The Forums for more useful details.
    Do not attempt to subvert or corrupt the software of the forum
    - members attempting to do so will be banned.
    No posts or signatures with intent to promote or advertise
    Any way of personal blogs/ websites/ pages/ affiliated websites/ resources are not allowed.* Links may be removed at Lenovo's discretion. Repeat offenders may face suspensions/ banning of accounts
    a) External Links 
    External links to other sites are permitted when they are relevant to the discussion and the information included is not available or cannot be found in the Lenovo forums or websites. Users are not permitted to repeatedly link or post threads with intention to link to personal blogs, websites or other personal resources in the web as this will be considered as advertising or board spamming. The links / posts will be removed at Lenovo's discretion. External links may not link to any site containing subjects listed in the Prohibitions section of these guidelines. Repeat offences will result in forum membership being revoked.
    b) Signatures
    Members are encouraged to include their system details in their signature as this will inform and assist others who may be offering advice. No pictures are permitted in signatures. A single discreet link to a personal website or other online resource is permitted in the signature line. However, the link must not be directed to any site containing subjects listed in the Prohibitions section of these guidelines. Members are not permitted to refer to the signature link in the body of their post text as this will be considered as advertising or board spamming.
    Guidelines and Recommendations
    Before creating a new thread, search the appropriate section of the forum first for any existing and related threads. It may be more constructive to all, to advance the knowledge of an existing thread than to create a possibly redundant one. If you find something similar, but believe your topic is unique enough to create a new thread, then do create the new thread choosing your title carefully (see below). Provide some comments as to the existence of the related thread(s) you found and link to them. This will help other users and the moderators to provide the most valuable responses possible.
    Post to the correct area - Post new threads in the sections for the particular family of systems, Thinkpads, Thinkcentres, Lenovo 3000, etc. Choose the proper series of systems - T, X, G, H, etc. Moderators will move threads to appropriate sections.
    Title threads appropriately. The title of a thread should accurately reflect the subject of the discussion and be as technically specific as possible.  Avoid inflammatory or emotional statements that do not aid the development of the conversation. Thread titles are indexed not only for search functions within the forum, but often externally in Google, Yahoo, etc. Proper thread titles will aid the active members of the Lenovo community, as well as non-members who may be searching more broadly. Example of a good thread title: T Thinkpad Blue Screens after suspend . Example of a bad thread title: Stupid computer locks up - worthless piece of junk. Moderators may alter thread titles to be more meaningful if less than appropriate titles are chosen.
    Use pictures to aid understanding and comprehension when appropriate. Screen captures of settings, pull down menus, or error messages can be very helpful in understanding an issue and helping to resolve it. Digital pictures of systems and their environments can also be helpful from time to time. Host pictures externaly, or post to photos area. Limit size to 100K or less. 10M pixel cameras are cool but the resulting file sizes are not. You can check out this article About Posting Pictures In The Forums for more useful details.
    Look for ways to advance the richness of the forum. Share awareness of this forum with other users of Lenovo products that you know. Participate in special interest areas. Look for opportunities to mentor junior members - help them along the path to greater knowledge, share shortcuts. Do link to external resources and documents. Members that distinguish themselves by consistently providing quality answers, that advance the collective understanding, and resolve specific problems will attain higher rankings and privileges.
    Please restrict off topic discussions to the general area.
    There are thousands of online communities dedicated to a wide variety of topics from automobiles, to astronomy, folk arts to fly fishing. This community is dedicated to the Lenovo family of products, services, and the community members who own, use, and benefit from them.
    Country Location
    - Members should denote their country location in their personal profile.  Location is important when offering advice, as sales, service, and product options may not be consistent country to country. Note that community members from other countries may not all share the same understanding of metaphors, social references, or slang expressions. Posts authored with this in mind may be more easily understood by all.  This field is a requirement during registration.
    DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITY
    Lenovo assumes no responsibility regarding the accuracy of the information posted on these pages, whether posted by third parties or by Lenovo representatives, and use of such information is at the recipient's own risk. While Lenovo provides no warranties or guarantees that any reported problems may be resolved with the use of any information available on these pages. By furnishing information, Lenovo does not grant any licenses to any copyrights, patents or any other intellectual property rights.
    You agree to indemnify and hold Lenovo and its affiliates and subsidiaries, and each of their employees, officers and agents harmless from any claim, including attorneys' fees, made by any third party arising out of content you submit, post, transmit or make available through these pages, your use of these pages, your violation of these Rules or the website Terms of Use and Privacy Policy, or your violation of any other third party's rights. This disclaimer and limitation of liability is in addition to any additional statements contained in the general Terms of Use posted on Lenovo's websites.
    Message Edited by Mark_Lenovo on 11-27-2007 03:43 AM
    ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
    Mark Hopkins
    Program Manager, Lenovo Social Media (Services)
    twitter @lenovoforums
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

    Hi
    It is unfortunate that you have a broken backspce key .  I would request you to visit the nearest service station to have the keyboard fixed   So please visit the below mentioned web link and locate the nearest service centre where you will be assisted by our service representatives.
    http://consumersupport.lenovo.com/ph/en/Maintenanc​estation/APR_Maintenancestation.aspx
    Hope This Helps
    Cheers!!! 

  • Mac Pro and Radeon 2600 HD Snow Leopard 10.6.7 and 10.6.8 Crash

    I have a Mac Pro, 2009 quad core xeon 2.8ghz with a ATI Radeon 2600 HD video card.  The computer is running 10.6.8 currently.  With 10.6.7 and 10.6.8 the comptuer crashes frequently.  Looking through the logs, I see some errors thrown by the kernel when it crashes.  There are some relating to the WindowServer, which reports as being "stuck" by the process monitor.  When this happens, the screen locks up and nothing on the screen moves except the mouse.  If I was watching a movie for example, the movie on the screen would freeze but the audio would continue to play.  I am still able to ssh into the computer and send a shutdown command to turn it off (or my wife powers it down by hitting the button).  It is driving me nuts trying to figure out what's going on.
    Steps I have taken to correct this:
    Reinstall OS from scratch on another disk 10.6 to 10.6.7 combo updater
    Flash the PRAM
    Run the computer's diagnostic utility from original disk (ran three times, no problems detected)
    Reinstall OS from scratch on yet another disk 10.6 to 10.6.8 combo updater
    Remove all USB and Firewire devices
    Smash head against screen and table
    Steps not taken yet
    buy new computer
    buy new video card
    smash computer in frustration
    Below are the log files for my last crash from this morning.  At 7:43, I woke the computer from sleep.  The following is everything that is displayed in the All messages section of the console until a reboot.  Anyone have any idea on how to fix this or what I can do?  Any help would be appreciated.
    6/26/11 7:43:02 AM    kernel    Wake reason = UHC2
    6/26/11 7:43:02 AM    kernel    System Wake
    6/26/11 7:43:02 AM    kernel    Previous Sleep Cause: 5
    6/26/11 7:43:02 AM    kernel    The USB device USB Receiver (Port 1 of Hub at 0x3d000000) may have caused a wake by issuing a remote wakeup (2)
    6/26/11 7:43:05 AM    kernel    Ethernet [Intel8254x]: Link up on en1, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [792d,af48,0de1,0e00,cde1,2c00]
    6/26/11 7:43:08 AM    kernel    USBF:    12269.568    AppleUSBEHCI[0xadd8000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 7, EP: 0)
    6/26/11 7:43:08 AM    configd[14]    network configuration changed.
    6/26/11 7:43:08 AM    configd[14]    network configuration changed.
    6/26/11 7:43:26 AM    ntpd[40]    time reset +0.747704 s
    6/26/11 7:50:15 AM    kernel    ** Device in slot: SLOT-1 **
    6/26/11 7:50:15 AM    kernel    ** GPU Debug Info Start **
    6/26/11 7:50:15 AM    kernel    0x00009588
    6/26/11 7:50:15 AM    kernel    0x000000d6
    6/26/11 7:50:15 AM    kernel    0x00000001
    6/26/11 7:50:15 AM    kernel    0x00000018
    6/26/11 7:50:16 AM    kernel    0x000090a2
    6/26/11 7:50:16 AM    kernel    0x00000001
    6/26/11 7:50:16 AM    kernel    0x00000001
    6/26/11 7:50:16 AM    kernel    0x00009588
    6/26/11 7:50:16 AM    kernel    0x00000001
    6/26/11 7:50:16 AM    kernel    0x00000015
    6/26/11 7:50:16 AM    kernel    0x00000000
    6/26/11 7:50:16 AM    kernel    0x00000001
    6/26/11 7:50:16 AM    kernel    0x00000047
    6/26/11 7:50:16 AM    kernel    0x00000000
    6/26/11 7:50:16 AM    kernel    0x00000001
    6/26/11 7:50:16 AM    kernel    0x00000058
    6/26/11 7:50:16 AM    kernel    0x00000011
    6/26/11 7:50:16 AM    kernel    0x00000001
    6/26/11 7:50:16 AM    kernel    0x00000055
    6/26/11 7:50:16 AM    kernel    0x00000000
    6/26/11 7:50:16 AM    kernel    0x00000001
    6/26/11 7:50:16 AM    kernel    0x0000004a
    6/26/11 7:50:16 AM    kernel    0x0000106b
    6/26/11 7:50:16 AM    kernel    0x00000001
    6/26/11 7:50:16 AM    kernel    0x0000004d
    6/26/11 7:50:16 AM    kernel    0x000000a6
    6/26/11 7:50:16 AM    kernel    0x00000000
    6/26/11 7:50:16 AM    kernel    0x00000010
    6/26/11 7:50:16 AM    kernel    0x00632800
    6/26/11 7:50:16 AM    kernel    0x00000000
    6/26/11 7:50:16 AM    kernel    0x00000021
    6/26/11 7:50:16 AM    kernel    0x00000081
    6/26/11 7:50:16 AM    kernel    0x00000000
    6/26/11 7:50:16 AM    kernel    0x00000011
    6/26/11 7:50:16 AM    kernel    0x00000007
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x00002254
    6/26/11 7:50:16 AM    kernel    0x00f8fc00
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x0000230c
    6/26/11 7:50:16 AM    kernel    0x00000001
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x0000263d
    6/26/11 7:50:16 AM    kernel    0x00000001
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x0000263c
    6/26/11 7:50:16 AM    kernel    0x00008a12
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021a0
    6/26/11 7:50:16 AM    kernel    0x80838645
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x0000219f
    6/26/11 7:50:16 AM    kernel    0x00028446
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x0000219d
    6/26/11 7:50:16 AM    kernel    0x01000000
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x0000219e
    6/26/11 7:50:16 AM    kernel    0x00001000
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021da
    6/26/11 7:50:16 AM    kernel    0x0a00340d
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021db
    6/26/11 7:50:16 AM    kernel    0x000000e0
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021dc
    6/26/11 7:50:16 AM    kernel    0x00000020
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021dd
    6/26/11 7:50:16 AM    kernel    0x000001a9
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021e0
    6/26/11 7:50:16 AM    kernel    0x0090009d
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021e1
    6/26/11 7:50:16 AM    kernel    0x00e000ed
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021e2
    6/26/11 7:50:16 AM    kernel    0x01600160
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021e3
    6/26/11 7:50:16 AM    kernel    0x00500050
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021e4
    6/26/11 7:50:16 AM    kernel    0x00e000e0
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021e5
    6/26/11 7:50:16 AM    kernel    0x003a01e3
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x000021b6
    6/26/11 7:50:16 AM    kernel    0x20000000
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x00003041
    6/26/11 7:50:16 AM    kernel    0x00100f0d
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x00003040
    6/26/11 7:50:16 AM    kernel    0x00100010
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x00003042
    6/26/11 7:50:16 AM    kernel    0x00001c80
    6/26/11 7:50:16 AM    kernel    0x00000002
    6/26/11 7:50:16 AM    kernel    0x00003043
    6/26/11 7:50:16 AM    kernel    0x10000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x000021c0
    6/26/11 7:50:17 AM    kernel    0x00002e00
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00003045
    6/26/11 7:50:17 AM    kernel    0x00003380
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00001508
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00000b00
    6/26/11 7:50:17 AM    kernel    0x8f100101
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00000bd1
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00000190
    6/26/11 7:50:17 AM    kernel    0x00121323
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00000504
    6/26/11 7:50:17 AM    kernel    0x00492491
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x0000050c
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00000545
    6/26/11 7:50:17 AM    kernel    0x000030c0
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00000503
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00002000
    6/26/11 7:50:17 AM    kernel    0x00000010
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00002004
    6/26/11 7:50:17 AM    kernel    0xa01034e0
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00002005
    6/26/11 7:50:17 AM    kernel    0x00000003
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x000021a3
    6/26/11 7:50:17 AM    kernel    0x00100000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00002016
    6/26/11 7:50:17 AM    kernel    0x90008880
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00000390
    6/26/11 7:50:17 AM    kernel    0x000003ff
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00000394
    6/26/11 7:50:17 AM    kernel    0x200000c0
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00000391
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x0000380a
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00003808
    6/26/11 7:50:17 AM    kernel    0xc0000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00003caa
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00003c80
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00001576
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x0000340d
    6/26/11 7:50:17 AM    kernel    0x44c83d57
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00003409
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x0000340a
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00003401
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00003400
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00003402
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x0000340c
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x00000980
    6/26/11 7:50:17 AM    kernel    0x00003005
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x000009b9
    6/26/11 7:50:17 AM    kernel    0x00000000
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:17 AM    kernel    0x000009b5
    6/26/11 7:50:17 AM    kernel    0x660ee616
    6/26/11 7:50:17 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x000021a4
    6/26/11 7:50:18 AM    kernel    0x00100010
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x000009b2
    6/26/11 7:50:18 AM    kernel    0x00000f23
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00000a23
    6/26/11 7:50:18 AM    kernel    0x00000f00
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00000a13
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00000a1d
    6/26/11 7:50:18 AM    kernel    0x00888888
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002284
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x000022f8
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002294
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x000022f4
    6/26/11 7:50:18 AM    kernel    0x00a030e0
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x0000223c
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x0000225c
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002256
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x000021b8
    6/26/11 7:50:18 AM    kernel    0x64000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00000fc0
    6/26/11 7:50:18 AM    kernel    0x00000001
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00000fd3
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00000fd1
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00000efb
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x000025c0
    6/26/11 7:50:18 AM    kernel    0x000003c0
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x000025c1
    6/26/11 7:50:18 AM    kernel    0x00000008
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x000025c6
    6/26/11 7:50:18 AM    kernel    0x00000020
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x0000233a
    6/26/11 7:50:18 AM    kernel    0x00008008
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002582
    6/26/11 7:50:18 AM    kernel    0x00000080
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002580
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002583
    6/26/11 7:50:18 AM    kernel    0x00007fe0
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002581
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x0000233e
    6/26/11 7:50:18 AM    kernel    0x000000f0
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002358
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002359
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x0000235a
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x0000235b
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x0000233f
    6/26/11 7:50:18 AM    kernel    0x00000000
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002300
    6/26/11 7:50:18 AM    kernel    0xe4000009
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002301
    6/26/11 7:50:18 AM    kernel    0x40240054
    6/26/11 7:50:18 AM    kernel    0x00000002
    6/26/11 7:50:18 AM    kernel    0x00002302
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002303
    6/26/11 7:50:19 AM    kernel    0x040404b4
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002304
    6/26/11 7:50:19 AM    kernel    0x00400040
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002305
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002140
    6/26/11 7:50:19 AM    kernel    0x0066ba1b
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002640
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002641
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002642
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002643
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002644
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002645
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002646
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002647
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002648
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002649
    6/26/11 7:50:19 AM    kernel    0x00180000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x0000264a
    6/26/11 7:50:19 AM    kernel    0x18002105
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x0000264b
    6/26/11 7:50:19 AM    kernel    0x3f7f7f3f
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x0000264c
    6/26/11 7:50:19 AM    kernel    0x40004000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x0000264d
    6/26/11 7:50:19 AM    kernel    0x00012100
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x0000264e
    6/26/11 7:50:19 AM    kernel    0x1f000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x0000264f
    6/26/11 7:50:19 AM    kernel    0xaaaa5555
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002650
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002651
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002652
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002653
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002654
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002655
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002656
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002657
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002658
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x00002659
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x0000265a
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x0000265b
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:19 AM    kernel    0x00000002
    6/26/11 7:50:19 AM    kernel    0x0000265c
    6/26/11 7:50:19 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000265d
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000265e
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000265f
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002660
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002661
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002662
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002663
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002664
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002665
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002666
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002667
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002668
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002669
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000266a
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000266b
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000266c
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000266d
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000266e
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000266f
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002670
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002671
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002672
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002673
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002674
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002675
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002676
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002677
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002678
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x00002679
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000267a
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000267b
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000267c
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:20 AM    kernel    0x0000267d
    6/26/11 7:50:20 AM    kernel    0x00000000
    6/26/11 7:50:20 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x0000267e
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x0000267f
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000008
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x001000c2
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x0000542b
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x0000542c
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00005431
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00005400
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00008000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00002b40
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000320
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000ce1
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00004102
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x008b8800
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x000a0008
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000180
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000020
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000000
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x00000008
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x001000c2
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x0000240b
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:21 AM    kernel    0x0000241d
    6/26/11 7:50:21 AM    kernel    0x00000002
    6/26/11 7:50:21 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00002406
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00002400
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00000001
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00300063
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00000001
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x002000c6
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000002
    6/26/11 7:50:22 AM    kernel    0x00002442
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:22 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM    kernel    0x00000000
    6/26/11 7:50:23 AM   

    I ran in safe mode for a while.  No hangups.  I then pulled the usb from the monitor and rebooted to try starting normally. 
    I was able to log in to my account (wife and I have different logins) and then it hung while loading the desktop.  this is the log from boot time to hangup...
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    PAE enabled
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    64 bit mode enabled
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    vm_page_bootstrap: 1533479 free pages and 31193 wired pages
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    standard timeslicing quantum is 10000 us
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    mig_table_max_displ = 73
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    AppleACPICPU: ProcessorId=2 LocalApicId=2 Enabled
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    AppleACPICPU: ProcessorId=3 LocalApicId=3 Enabled
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    AppleACPICPU: ProcessorId=4 LocalApicId=6 Enabled
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    AppleACPICPU: ProcessorId=5 LocalApicId=7 Enabled
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    AppleACPICPU: ProcessorId=6 LocalApicId=4 Enabled
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    AppleACPICPU: ProcessorId=7 LocalApicId=5 Enabled
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    calling mpo_policy_init for TMSafetyNet
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    Security policy loaded: Safety net for Time Machine (TMSafetyNet)
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    calling mpo_policy_init for Quarantine
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    Security policy loaded: Quarantine policy (Quarantine)
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    calling mpo_policy_init for Sandbox
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    Security policy loaded: Seatbelt sandbox policy (Sandbox)
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    Copyright (c) 1982, 1986, 1989, 1991, 1993
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    The Regents of the University of California. All rights reserved.
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    MAC Framework successfully initialized
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    using 16384 buffer headers and 4096 cluster IO buffer headers
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    IOAPIC: Version 0x20 Vectors 64:87
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    ACPI: System State [S0 S3 S4 S5] (S3)
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    PFM64 0x3f10000000, 0xf0000000
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    [ PCI configuration begin ]
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    console relocated to 0x3f10010000
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    PCI configuration changed (bridge=2 device=1 cardbus=0)
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    [ PCI configuration end, bridges 15 devices 26 ]
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    AppleIntelCPUPowerManagement: (built 16:44:45 Jun  7 2011) initialization complete
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    mbinit: done (64 MB memory set for mbuf pool)
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    FireWire runtime power conservation disabled. (2)
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    rooting via boot-uuid from /chosen: 9C5D82B8-EC43-3056-8CC4-98B54A43034B
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    com.apple.AppleFSCompressionTypeZlib kmod start
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    com.apple.AppleFSCompressionTypeZlib load succeeded
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    AppleIntelCPUPowerManagementClient: ready
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT0 @0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/ST31000528AS Media/IOGUIDPartitionScheme/Macintosh HD@2
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    BSD root: disk1s2, major 14, minor 6
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    jnl: unknown-dev: replay_journal: from: 64491008 to: 65744384 (joffset 0x1d1c000)
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    FireWire (OHCI) TI ID 823f built-in now active, GUID 001ff3fffe22e0ba; max speed s800.
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    USBMSC Identifier (non-unique): 303030303030303030303030 0x13fd 0x840 0x113
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    jnl: unknown-dev: journal replay done.
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    USBMSC Identifier (non-unique): 2HA4F4QM     0xd49 0x7310 0x125
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    USBMSC Identifier (non-unique): 0000000000000000W 0x13fd 0x1040 0x106
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    [Bluetooth::CSRHIDTransition] transition complete.
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    hfs: Removed 3 orphaned / unlinked files and 0 directories
    6/26/11 4:35:36 PM    localhost    kernel    kernel    0    kern    Debug    CSRUSBBluetoothHCIController::setupHardware super returned 0
    6/26/11 4:35:33 PM    localhost    com.apple.launchd[1]    com.apple.launchd    1    com.apple.console    Notice    *** launchd[1] has started up. ***
    6/26/11 4:35:36 PM    localhost    DirectoryService[11]    DirectoryService    11    daemon    Notice    Improper shutdown detected
    6/26/11 4:35:44 PM    localhost    kernel    kernel    0    kern    Debug    AppleIntel8254XEthernet: Ethernet address 00:1f:5b:32:b5:4c
    6/26/11 4:35:44 PM    localhost    kernel    kernel    0    kern    Debug    AppleIntel8254XEthernet: Ethernet address 00:1f:5b:32:b5:4d
    6/26/11 4:35:44 PM    localhost    kernel    kernel    0    kern    Debug    systemShutdown false
    6/26/11 4:35:44 PM    localhost    blued[16]    blued    16    user    Notice    Apple Bluetooth daemon started
    6/26/11 4:35:46 PM    localhost    mDNSResponder[18]    mDNSResponder    18    daemon    Error    mDNSResponder mDNSResponder-258.21 (May 26 2011 14:40:13) starting
    6/26/11 4:35:46 PM    localhost    com.apple.SecurityServer[28]    com.apple.SecurityServer    28    authpriv    Notice    Session 0x5fbff962 created
    6/26/11 4:35:46 PM    localhost    com.apple.SecurityServer[28]    com.apple.SecurityServer    28    authpriv    Notice    Entering service
    6/26/11 4:35:46 PM    localhost    kernel    kernel    0    kern    Debug    jnl: disk0s2: replay_journal: from: 51876864 to: 52925952 (joffset 0x15d5000)
    6/26/11 4:35:46 PM    localhost    kernel    kernel    0    kern    Debug    jnl: disk3s2: replay_journal: from: 43576320 to: 43658752 (joffset 0x1d1c000)
    6/26/11 4:35:46 PM    localhost    kernel    kernel    0    kern    Debug    jnl: disk2s2: replay_journal: from: 6728704 to: 7798272 (joffset 0x1d1c000)
    6/26/11 4:35:46 PM    localhost    kernel    kernel    0    kern    Debug    jnl: disk3s2: journal replay done.
    6/26/11 4:35:46 PM    localhost    kernel    kernel    0    kern    Debug    jnl: disk0s2: journal replay done.
    6/26/11 4:35:46 PM    localhost    kernel    kernel    0    kern    Debug    jnl: disk2s2: journal replay done.
    6/26/11 4:35:46 PM    localhost    kernel    kernel    0    kern    Debug    Previous Shutdown Cause: 0
    6/26/11 4:35:46 PM    localhost    kernel    kernel    0    kern    Debug    DSMOS has arrived
    6/26/11 4:35:46 PM    localhost    configd[15]    configd    15    user    Notice    network configuration changed.
    6/26/11 4:35:46 PM    localhost    kernel    kernel    0    kern    Debug    Ethernet [Intel8254X]: Link down on en1
    6/26/11 4:35:46 PM    MacPro    configd[15]    configd    15    user    Notice    setting hostname to "MacPro.local"
    6/26/11 4:35:47 PM    MacPro    kernel    kernel    0    kern    Debug    ** Device in slot: SLOT-1 **
    6/26/11 4:35:49 PM    MacPro    bootlog[66]    bootlog    66    com.apple.system.utmpx    Notice    BOOT_TIME: 1309120532 0
    6/26/11 4:35:49 PM    MacPro    fseventsd[59]    fseventsd    59    daemon    Critical    event logs in /Volumes/Burrito/.fseventsd out of sync with volume.  destroying old logs. (131 3 784)
    6/26/11 4:35:49 PM    MacPro    kernel    kernel    0    kern    Debug    Ethernet [Intel8254x]: Link up on en1, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [792d,af08,0de1,0e00,cde1,7c00]
    6/26/11 4:35:49 PM    MacPro    fseventsd[59]    fseventsd    59    daemon    Critical    log dir: /Volumes/Burrito/.fseventsd getting new uuid: 241DE7A7-24B4-455B-9D1B-B3DF5DF8C955
    6/26/11 4:35:49 PM    MacPro    com.apple.usbmuxd[49]    com.apple.usbmuxd    49    usbmuxd    Notice    usbmuxd-211 built on Feb  8 2011 at 13:49:43 on Feb  8 2011 at 13:49:43, running 64 bit
    6/26/11 4:35:49 PM    MacPro    /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[55]    /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow    55    user    Error    Login Window Application Started
    6/26/11 4:35:49 PM    MacPro    fseventsd[59]    fseventsd    59    daemon    Critical    event logs in /.fseventsd out of sync with volume.  destroying old logs. (339 17 784)
    6/26/11 4:35:50 PM    MacPro    fseventsd[59]    fseventsd    59    daemon    Critical    log dir: /.fseventsd getting new uuid: 1F784434-B9CD-4494-B6A5-B025C45D9F19
    6/26/11 4:35:52 PM    MacPro    configd[15]    configd    15    user    Notice    network configuration changed.
    6/26/11 4:35:52 PM    MacPro    com.apple.SecurityServer[28]    com.apple.SecurityServer    28    authpriv    Notice    Session 0x3a0c240 created
    6/26/11 4:35:52 PM    MacPro    com.apple.SecurityServer[28]    com.apple.SecurityServer    28    authpriv    Notice    Session 0x3a0c240 attributes 0x30
    6/26/11 4:35:52 PM    MacPro    com.apple.launchctl.LoginWindow[102]    com.apple.launchctl.LoginWindow    102    com.apple.console    Notice    launchctl: Dubious permissions on file (skipping): /Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist
    6/26/11 4:35:53 PM    MacPro    loginwindow[55]    loginwindow    55    auth    Error    Login Window Started Security Agent
    6/26/11 4:35:53 PM    MacPro    WindowServer[90]    WindowServer    90    com.apple.coregraphics    Error    kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    6/26/11 4:35:53 PM    MacPro    com.apple.WindowServer[90]    com.apple.WindowServer    90    com.apple.console    Notice    Sun Jun 26 16:35:53 MacPro.local WindowServer[90] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    6/26/11 4:35:53 PM    MacPro    SecurityAgent[109]    SecurityAgent    109    authpriv    Error    Showing Login Window
    6/26/11 4:35:55 PM    MacPro    warmd[48]    warmd    48    user    Warning    [fetcher_open_file:936] open("/var/db/dyld/dyld_shared_cache_x86_64") => -1 (errno: 2)
    6/26/11 4:36:22 PM    MacPro    SecurityAgent[109]    SecurityAgent    109    authpriv    Error    User info context values set for coutinho
    6/26/11 4:36:22 PM    MacPro    authorizationhost[107]    authorizationhost    107    authpriv    Error    Failed to authenticate user <coutinho> (tDirStatus: -14090).
    6/26/11 4:36:39 PM    MacPro    SecurityAgent[109]    SecurityAgent    109    authpriv    Error    User info context values set for coutinho
    6/26/11 4:36:40 PM    MacPro    SecurityAgent[109]    SecurityAgent    109    authpriv    Error    Login Window Showing Progress
    6/26/11 4:36:43 PM    MacPro    SecurityAgent[109]    SecurityAgent    109    authpriv    Error    Login Window done
    6/26/11 4:36:43 PM    MacPro    loginwindow[55]    loginwindow    55    auth    Error    Login Window - Returned from Security Agent
    6/26/11 4:36:43 PM    MacPro    loginwindow[55]    loginwindow    55    com.apple.system.lastlog    Notice    USER_PROCESS: 55 console
    6/26/11 4:36:43 PM    MacPro    com.apple.launchctl.Background[131]    com.apple.launchctl.Background    131    com.apple.console    Notice    launchctl: Dubious permissions on file (skipping): /Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist
    6/26/11 4:36:43 PM    MacPro    com.apple.launchctl.Aqua[132]    com.apple.launchctl.Aqua    132    com.apple.console    Notice    launchctl: Dubious permissions on file (skipping): /Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist
    6/26/11 4:36:43 PM    MacPro    com.apple.launchctl.Aqua[132]    com.apple.launchctl.Aqua    132    com.apple.console    Notice    launchctl: Dubious permissions on file (skipping): /etc/mach_init_per_user.d/com.adobe.SwitchBoard.monitor.plist
    6/26/11 4:36:43 PM    MacPro    com.apple.launchd.peruser.501[130]    com.apple.launchd.peruser.501    130    com.apple.console    Warning    (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    6/26/11 4:36:46 PM    MacPro    fontd[151]    fontd    151    com.apple.console    Warning    Database content version mismatch (stored(15) != expected(14))
    6/26/11 4:36:46 PM    MacPro    fontd[151]    fontd    151    com.apple.console    Error    Failed to open read-only database, regenerating DB
    6/26/11 4:36:50 PM    MacPro    com.apple.launchd.peruser.501[130]    com.apple.launchd.peruser.501    130    com.apple.console    Warning    (com.apple.Kerberos.renew.plist[159]) Exited with exit code: 1
    6/26/11 4:36:51 PM    MacPro    com.apple.launchd.peruser.501[130]    com.apple.launchd.peruser.501    130    com.apple.console    Warning    ([email protected][164]) Exited with exit code: 1
    6/26/11 4:36:52 PM    MacPro    com.apple.usbmuxd[49]    com.apple.usbmuxd    49    usbmuxd    Warning    HandleUSBMuxDictionary client 0x103400090-iTunesHelper/com.apple.iTunesHelper using library usbmuxd-211 built on Jan 13 2011 at 04:19:31, running usbmuxd-211 built on Feb  8 2011 at 13:49:43
    6/26/11 4:37:09 PM    MacPro    com.apple.fontd[151]    com.apple.fontd    151    com.apple.console    Notice    FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    6/26/11 4:37:11 PM    MacPro    mdworker[129]    mdworker    129    user    Error    (Error) SyncInfo: Catalog changed during searchfs too many times -- falling back to fsw search /
    6/26/11 4:37:13 PM    MacPro    com.apple.fontd[151]    com.apple.fontd    151    com.apple.console    Notice    FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    6/26/11 4:37:15 PM    MacPro    /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Support/genatsdb[180]    /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Support/genatsdb    180    user    Error    *GENATSDB* FontObjects generated = 646
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    ** Device in slot: SLOT-1 **
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    ** GPU Debug Info Start **
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00009588
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x000000d6
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000018
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x000090a2
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00009588
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000015
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000047
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000058
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000011
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000055
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000004a
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000106b
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000004d
    6/26/11 4:37:17 PM    MacPro    kernel    kernel    0    kern    Debug    0x000000a6
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000010
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00632800
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000021
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000081
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000011
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000007
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002254
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00f8fc00
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000230c
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000263d
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000263c
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00008a12
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021a0
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x80000645
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000219f
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000006
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000219d
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000219e
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00004000
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021da
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x0a00180d
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021db
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000000e0
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021dc
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000020
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021dd
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000200
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021e0
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000000d
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021e1
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x01000106
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021e2
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x01d001d0
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021e3
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00a800a8
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021e4
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00e000e0
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021e5
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00320032
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021b6
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003041
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00100f0d
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003040
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00100010
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003042
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003043
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x10000000
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021c0
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003e00
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003045
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000280
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00001508
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000b00
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x8f100101
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000bd1
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000190
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00121323
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000504
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00492491
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:18 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000050c
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000545
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000503
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000010
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002004
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0xa0003030
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002005
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000003
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021a3
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00100010
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002016
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x90008880
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000390
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x000003ff
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000394
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x200000c0
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000391
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000380a
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003808
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0xc0000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003caa
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003c80
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00001576
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000340d
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x44c83d57
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003409
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000340a
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003401
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003400
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003402
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000340c
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000980
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00003005
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x000009b9
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x000009b5
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x660ee616
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021a4
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00100010
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x000009b2
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000f23
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000a23
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000f00
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000a13
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000a1d
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00888888
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002284
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x000022f8
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002294
    6/26/11 4:37:19 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x000022f4
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00a030e0
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000223c
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000225c
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002256
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x000021b8
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000fc0
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000001
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000fd3
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000fd1
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000efb
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x000025c0
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x000003c0
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x000025c1
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000008
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x000025c6
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000020
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000233a
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00008008
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002582
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000080
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002580
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002583
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00007fe0
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002581
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000233e
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x000000f0
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002358
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002359
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000235a
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000235b
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000233f
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002300
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0xe4000009
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002301
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x40240054
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002302
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002303
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x04043088
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002304
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00280028
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002305
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002140
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x000009f5
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002640
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002641
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002642
    6/26/11 4:37:20 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002643
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002644
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002645
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002646
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002647
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002648
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002649
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00180000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000264a
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002007
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000264b
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x3f7f7f3f
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000264c
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x40004000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000264d
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00009000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000264e
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x1f000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000264f
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0xaaaa5555
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002650
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002651
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002652
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002653
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002654
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002655
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002656
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002657
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002658
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00002659
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x0000265a
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000000
    6/26/11 4:37:21 PM    MacPro    kernel    kernel    0    kern    Debug    0x00000002
    6/26/11

  • Rule to avoid sending email to the wrong recipient based on content

    Hi guys,
    My customer has had bad experience with the auto-complete feature in Outlook in the past, and now that he's getting Office 365 Enterprise, he wants to know if there is a way to block any outgoing mail intended for another company. We would be detecting the
    destination companies based on 1) company name mentioned somewhere in the email message and 2) company domain specified in the To, Cc and Bcc fields. Example:
    I write an email containing confidential information for John Smith from Contoso with the word "Contoso" used at some point in the email body. When I start typing the recipient's address, I inadvertently select another John Smith, this guy from
    Fabricam. If I click SEND, Fabricam will have sensitive information intended for Contoso.
    Hell breaks loose.
    So the solution comes from either Outlook (proactively via a mail-tip) or Exchange (in the background as a transport rule or DLP policy) stopping this from happening, but I can't for the life of me find how to create a rule that checks for a string of text
    in the body or subject and compares that to the recipient domain. If a match is found, the email should leave the org just as usual. If one is not found, the email should be either blocked, sent to a manager for approval, or the user warned.
    Oh, and the customer will primarily be using EOP1 or E1 plans, so I can't rely on DLP because that's on the EOP2 plans and our company doesn't offer them.
    ¿Has anybody pulled one of these off in the past? It seems like such a simple scenario yet it doesn't seem straightforward enough.
    Thanks!

    Hi Gregory,
    i do believe your best bet would still be DLP, but i just check on one of our EOP1 customers and there is a possibility to create a Rule (under Mailflow in Exchange admin) that checks on subject and body contents. Hopefully that will allow you to create
    the setup you need.
    Kind regards, Philipp - Solid IT Solutions

  • How do i change read/write permission on an external hard drive?

    how do i change read/write permissions for an external hard drive?

    If, on the otherhand, you are trying to write to a drive that is formatted NTFS (for Windows), and can't.
    You have two choices...
    1. Reformat the drive. Either Mac OS format, if you are using this only on your Mac. Or ExFAT, or FAT 32 if you intend to use it on both a Mac OS computer and a Windows unit. note: ExFAT is not suported by XP.
    2. Install one of the drivers necessary for the Mac to write to a NTFS volume. Unless you want the experience of having the support for this being one that is sporadic, avoid this. I used to be a strong proponent of NTFS-3G, until I started having the problems with Lion, that many users warned us about. Go this route only if you find you must use NTFS on your drive. Paragon and Tuxtera are the sources for these.

  • Upgrade 10.3 to 10.4: Kerberos authentication stopped working

    Hello:
    I upgraded a G5 XServe from 10.3.9 to 10.4. It almost worked - ie: system booted again, all disks are visible, etc. But, trying to log on with a user in the OD hosted on that machine has stopped working... this happens when I try to mount a shared AFP volume, and also when logging on from a 10.4.8 client bound in Directory Access to that server. Logging on under the admin account at the console (over ARD in this case), or via ssh, works fine. I didn't think to try other accounts via that method, I will do this tomorrow morning local time and post a followup.
    Upon connecting to the server with Server Admin, a message told me that there were new services which needed kerberizing, and to go to Open Directory and click 'settings'. I did this, and also looked at the overview: netinfod was in local-only mode, while all the others were marked as "Running" (lookupd, slapd, Password Server, Kerberos). In the old 10.3.9 system (ie: where user authentication is working OK), all are marked as "Running".
    I clicked the "Kerberize" button, and entered a directory admin username and password as instructed. I think the process completed (unfortunately I didn't get a screenshot). Now, the kerberize button is gone.
    At various times when admin passwords were requested, I have to try several; the expected ones didn't always work. Eg: I thought the "diradmin" account was needed in one dialog, but I used the system "admin" account instead. (Sorry, didn't record proper details of those events).
    Forward and reverse DNS lookups with the host command work ok - they return the expected IP address.
    I looked through a bunch of logs (/var/log/*.log, /Library/Logs/.../*.log), and found a few lines with possible clues... these are shown further down.
    I have now tried updating to 10.4.8 (I'm not sure if I should have done it before kerberos was going again, but getting the system up to date does seem prudent). Errors are all exactly the same.
    Any hints or suggestions much appreciated! Here's some promising things I've found, which I'll be studying today. I hope to take the server down tomorrow morning again to try this stuff out...
    http://lists.apple.com/archives/macos-x-server/2006/Feb/msg01152.html
    http://lists.apple.com/archives/Client-management/2006/Sep/msg00013.html
    Thanks,
    Ralph
    /var/log/system.log:
    Mar 10 15:18:37 tararuas krb5kdc[84]: no sockets set up?
    AppleFileServiceAccess.log:
    IP 130.195.240.52 - - [10/Mar/2007:15:15:15 1200] "Logout test333" -5023 0 0
    IP 130.195.240.52 - - [10/Mar/2007:15:24:30 1200] "Logout ralphwahrlich" -5023 0 0
    FWIW, the AFP Reference gives error -5023 meaning thus: "UAM failed (the specified old password doesn’t match); no user is logged in yet for the specified session; authentication failed; password is incorrect."
    From slapconfig.log (slightly edited for brevity):
    slapconfig.log:
    2007-03-10 14:51:52 +1300 - slapconfig -migrateldapserver
    2007-03-10 14:51:52 +1300 - 1 Removing LDAP server from search policy
    2007-03-10 14:51:52 +1300 - 2 Data export
    2007-03-10 14:51:52 +1300 - command: /usr/sbin/oldslapcat -c -l /var/db/openldap/migration/backup.ldif
    2007-03-10 14:51:53 +1300 - Removed file at path /var/db/openldap/openldap-data/__db.001.
    2007-03-10 14:51:53 +1300 - Removed file at path /var/db/openldap/openldap-slurp/replication.log.lock.
    2007-03-10 14:51:53 +1300 - command: /usr/sbin/NeST -pwsrekey
    2007-03-10 14:51:55 +1300 - NeST command output:
    nothing found to load
    2007-03-10 14:51:55 +1300 - 3 Data import
    2007-03-10 14:51:55 +1300 - command: /usr/sbin/slapadd -c -l /tmp/backup11774.ldif
    2007-03-10 14:51:58 +1300 - 4 Updating LDAP configuration
    2007-03-10 14:51:59 +1300 - Starting LDAP server (slapd)
    2007-03-10 14:52:22 +1300 - 5 Updating data in LDAP
    2007-03-10 14:52:22 +1300 - command: /usr/bin/ldapdelete -c -x -H ldapi://%2Fvar%2Frun%2Fldapi cn=ldapreplicas,cn=config,dc=geo,dc=vuw,dc=ac,dc=nz cn=passwordserver,cn=config,dc=geo,dc=vuw,dc=ac,dc=nz cn=passwordserver_4AB32E0671171DC872A9D40CC42F9E07,cn=config,dc=geo,dc=vuw,dc=a c,dc=nz
    2007-03-10 14:52:22 +1300 - ldapdelete command output:
    ldap_bind: Can't contact LDAP server (-1)
    2007-03-10 14:52:22 +1300 - ldapdelete command failed with status 1
    2007-03-10 14:52:22 +1300 - command: /usr/bin/ldapadd -c -x -H ldapi://%2Fvar%2Frun%2Fldapi
    2007-03-10 15:03:55 +1300 - slapconfig -setmacosxodpolicy
    2007-03-10 15:03:55 +1300 - command: /usr/bin/ldapadd -c -x -H ldapi://%2Fvar%2Frun%2Fldapi
    2007-03-10 15:03:55 +1300 - ldapadd command output:
    ldap_modify: No such object (32)
    matched DN: cn=config,dc=geo,dc=vuw,dc=ac,dc=nz
    2007-03-10 15:03:55 +1300 - ldapadd command failed with status 32
    2007-03-10 15:04:13 +1300 - slapconfig -kerberize
    2007-03-10 15:04:13 +1300 - Error: Incorrect username or password. You must enter a directory domain administrator username and password.
    2007-03-10 15:05:25 +1300 - slapconfig -setmacosxodpolicy
    2007-03-10 15:05:25 +1300 - command: /usr/bin/ldapadd -c -x -H ldapi://%2Fvar%2Frun%2Fldapi
    2007-03-10 15:05:25 +1300 - ldapadd command output:
    ldap_modify: No such object (32)
    matched DN: cn=config,dc=geo,dc=vuw,dc=ac,dc=nz
    2007-03-10 15:05:25 +1300 - ldapadd command failed with status 32
    2007-03-10 15:05:38 +1300 - slapconfig -kerberize
    2007-03-10 15:05:38 +1300 - Error: Incorrect username or password. You must enter a directory domain administrator username and password.
    2007-03-10 15:05:44 +1300 - slapconfig -kerberize
    2007-03-10 15:05:45 +1300 - Removed directory at path /var/db/krb5kdc.
    2007-03-10 15:05:45 +1300 - command: /sbin/kerberosautoconfig -r GEO.VUW.AC.NZ -m tararuas.geo.vuw.ac.nz -u -v 1
    2007-03-10 15:05:45 +1300 - kerberosautoconfig command failed with exception launch path not accessible
    2007-03-10 15:05:45 +1300 - command: /usr/sbin/kdcsetup -f /LDAPv3/127.0.0.1 -w -a admin -p ** -v 1 GEO.VUW.AC.NZ
    2007-03-10 15:05:47 +1300 - kdcsetup command output:
    Contacting the Directory Server
    Authenticating to the Directory Server
    Creating Kerberos directory
    Creating KDC Config File
    Creating Admin ACL File
    Creating Kerberos Master Key
    Creating Kerberos Database
    Creating Kerberos Admin user
    WARNING: no policy specified for [email protected]; defaulting to no policy
    Adding kerberos auth authority to admin user
    Creating keytab for the admin tools
    Adding KDC & kadmind to launchd
    Adding the new KDC into the KerberosClient config record
    AddKDCToConfig: KDC is already present in record
    Finished
    2007-03-10 15:05:47 +1300 - command: /usr/sbin/mkpassdb -kerberize
    Mac Mini G4 1.25GHz   Mac OS X (10.4.8)  

    Thanks heaps for your reply
    Yes, I did indeed use CDs.
    I followed the instructions at http://docs.info.apple.com/article.html?artnum=301909-en , but struck problems...
    Step 16:
    here's what I got after pressing CTRL-D:
    ldap_add: Server is unwilling to perform (53)
    additional info: no global superior knowledge
    I thought I'd press ahead anyway... and struck the next problem:
    Step 18:
    here's what I got when attempting to add a record in /AccessControls.. a dialog box that said this:
    Record type not mapped
    The record with type "AccessControls" is not mapped. Your should report this error to the administrator of your directory server.
    I found the following:
    http://docs.info.apple.com/article.html?path=ServerAdmin/10.4/en/c7od31.html
    step 8 on that page, bullet point starting with "To add a mapping for a record type ..." seems what I want, but have no idea which object class name to use.
    Not sure where to go next. I'm somewhat inclined to blow away the OD database, and rebuild it from a backup. I would do this...
    On the 10.3.9 system:
    - export the OD from WGM
    Go into 10.4.8, and:
    - in Server Admin, change OD to be standalone only
    - reboot
    - go back to Server Admin, change OD to be a OD master
    - import the records exported from the 10.3.9 system
    I will post another update tommorrow.

Maybe you are looking for