Saturday, May 31, 2008
More LifeLock Discounts
It’s sort of like that when you get the LifeLock discount: When you enroll in LifeLock’s identity theft prevention program, you know you’re doing something good for yourself. LifeLock.com protects your good name, your credit, and your financial security. Plus, you get peace of mind from knowing that if your wallet ever goes missing, their WalletLock service means help will be close at hand. If you have a family, providing that protection and security is something you have to do for them, too.
Enroll now using the LifeLock discount, and you get all that protection and security, and you get to save money, too. With Promotion Code RD32, you get the very best price available to new LifeLock customers. But, just because you’re taking advantage of the LifeLock discount, doesn’t mean you have to settle for less. LifeLock gives you lots of options so you can be sure you’re getting the plan that works best for you.
You decide which plan and payment suits you best
You can read the lifelock reviews decide whether you want to pay by the month or by the year. With the discount, an annual plan costs as little as $99—that’s $21 less than the regular price. If you decide to pay by the month, you pay as little as $9—and over the course of a year, you still save $12. Whichever you choose, the LifeLock discount even gives you your first month of protection completely free.
If you have children, you should know that every year 400,000 kids are victims of identity theft, according to the Federal Trade Commission. But, LifeLock is one of the few companies that will provide identity theft protection, and with the LifeLock discount, you can get that protection for as little as $22.50 for a year, or $2.25 a month. With either plan your child receives a free month just like you.
Do it now
Why wait? Use a lifelock promo code and feel good about protecting yourself from identity theft–and enjoy the good feeling that comes from saving money, too!
FREE products from lifelock.com
The lifelock TrueAddress™ product protects you from identity thieves who would change your address so your mail is delivered to a location where they can collect it. Once they have your mail, they have easy access to a treasure trove of information they can use to steal your identity. Another reason identity thieves change their victims’ address is to delay the discovery of the new accounts they’ve opened in their victims’ name. If you’re not getting the bills, how long would it take you to find out you’ve become a victim of identity theft?
The LifeLock.com TrueAddress™ product makes sure that never happens. Using internet technology, LifeLock’s new product searches the internet to see if one of the 45 million addresses changes submitted every year is for you. If it is, they notify you immediately.
eRecon™ works on the internet in the same way, monitoring for your email address, Social Security number, account numbers and driver’s license numbers—a digital reconnaissance of the worldwide web to make sure your personal information isn’t being bought, sold or traded by identity thieves.
Check out the lifelock promotion code to receive the best discount available and signup to get these FREE products
Even the identity of life lock CEO was stolen
Davis is the first to say that no identity theft protection system can guarantee you’ll never be attacked by an identity thief. But in true lemons-to-lemonade style, Davis explains on lifelock review that what happened to him is a good example of how LifeLock work: the incident was covered by the LifeLock $1 million guarantee, and didn’t cost him a penny.
If you’ve never read the lifelock reviews by consumers, it’s time you learned more about how LifeLock can protect you from identity theft. If you’ve already been to the website, it’s worth going back to see their response to the nuisance lawsuits being filed against them.
And, whether or not you’ve already been to the site, if you’re an auto racing fan you should check out the new pages and videos. You can even vote for your all-time favorite racing hero, with the winner being announced on ABC September 28.
Sunday, May 18, 2008
life lock can protect you from the pirate suit scene
You have seen the commercial about a guy who is forced to work in fish food restaurant and wears a pirate suit all because some hacker stole his identity.
And if you dont want to be there in the same restuarant every evening serving chowder and iced tea and ending up selling fish to tourists in t-shirts, you definitely need to check out lifelock.
Thursday, May 15, 2008
Informatica 8.5.1 Issues - Summary
An error occurs when you use the Teradata DataDirect 5.2 ODBC driver with the PowerCenter Client.
Workaround: Use the Teradata ODBC driver.
174593: Pmrepagent process for the Repository Service might leak memory when you use the Oracle 10.2.0.x client
The Repository Service process might leak memory when it runs on a 64-bit Linux machine, and you use Oracle 10.2.0.x client to connect to the repository.
PowerCenter Limitations
178363: The Integration Service shuts down unexpectedly on AIX 32-bit when you run a session that generates a Sorter cache larger than 2 GB
The Integration Service shuts down unexpectedly when you run a session that contains a Sorter transformation on AIX 32-bit and the size of the Sorter cache exceeds 2 GB.
177814: Session configured with resume recovery strategy fails in PowerCenter 8.5.1 because columns are missing from the recovery tables
After upgrading to PowerCenter 8.5.1, a session configured with the resume recovery strategy might fail because columns do not exist in the PM_RECOVERY and PM_REC_STATE tables.
The Integration Service attempts to dynamically add these columns the first time the session runs in 8.5.1.
The SQL statement to alter the tables might fail for the following reasons:
The user does not have the privileges to alter the tables.
The database returns an error before the Integration Service performs the ALTER statement and the session fails.
Workaround: Manually update each instance of the PM_RECOVERY and PM_REC_STATE tables. The scripts to alter the tables are in the following folder:
[PowerCenter Installation_dir]/server/bin/RecoverySQL
For more information see Informatica Knowledge Base article 22999.
177564: Sessions that contain a Java transformation fail on HP-UX 32-bit
When the Integration Service preloads the JVM library on HP-UX 32-bit, it cannot enable any service. Therefore, sessions that contain a Java transformation fail.
Workaround: Set the LD_PRELOAD environment variable for the Integration Service process to
177338, 177337, 177336: Web service workflow that contains a web service target definition created in the Target Designer can generate errors during execution
In the Target Designer, you can create a web service target definition by selecting Targets > Web Service Provider > Create Web Service Definition. When you run a web service workflow that contains a web service target definition created this way, the workflow can fail.
Workaround: Do not create a web service target definition from a relational or flat file source or target in the Target Designer. To create a web service target definition from a relational or flat file source or target, create it at the same time you create the source definition. In the Source Analyzer, select Sources > Web Service Provider > Create Web Service Definition. On the Create Web Service Definition window, select the Create Target option. Make sure that the Create Source and Create Target options are selected.
176736: Import Mapping Template Wizard fails when you import a slowly changing dimension Type 2 effective date mapping or Type 3 mapping
When you import a slowly changing dimension Type 2 effective date mapping or Type 3 mapping and you used the Create Target option, the Import Mapping Template Wizard fails.
Workaround: If you are using an Oracle source or target, change the ports with Timestamp datatype to date datatype.
176735: Import Mapping Template Wizard fails when you import a slowly changing dimension Type 3 mapping
When you import a slowly changing dimension Type 3 mapping with or without duplicate row handling and you use the Create Target option, the Import Mapping Template Wizard fails.
Workaround: If you are using an Oracle source or target, change the ports with Timestamp datatype to date datatype.
176733: Session with slowly changing dimension Type 2 mapping with version number with or without duplicate row handling fails
Session with slowly changing dimension Type 2 mapping with version number with or without duplicate row handling fails when you use a Microsoft SQL Server source or target.
176730: Session fails unexpectedly while running a dynamic Lookup transformation with an unprojected associated port
A PowerCenter session running a dynamic Lookup transformation fails unexpectedly if a lookup port with an associated port is not projected to another transformation or target.
176439: Moving a Reporting Service from one domain to another results in the user accounts being deleted
If you move a Reporting Service from one domain to another and use the Data Analyzer repository information that you specify in the old domain, the synchronization process deletes all the user accounts that do not exist in the new domain. The Reporting Service does not update the Data Analyzer repository with the information contained in the new domain.
Workaround: Add the users that exist in the original domain to the new domain before you move the Reporting Service. You can also move the users to the LDAP directory service and import them to the new domain, or import the users from the native domain.
176204: UTF-16 and UTF-32 encoding of line feed and carriage return is incorrect for big endian or little endian flat file targets
UTF-16 and UTF-32 encoding of line feed and carriage return for big endian or little endian flat file targets is incorrect.
176143: Importing a flat file source or target that contains a Shift-JIS character and scrolling the preview pane causes the Designer to freeze
If you import a flat file source or target that contains a Shift-JIS character using the Designer Flat File Import Wizard and scroll the preview pane horizontally, the Designer freezes.
176088: Source definitions created from an XML file with Japanese encoding that are then exported from the repository cannot be imported back into the repository
For example, you import a source definition from an XML file that has Shift-JIS (SJIS) encoding. After the source definition is created, export the source to a PowerCenter export file. If you import the file back to the repository, the import process fails.
175920: Load Manager API version 8.5 is not compatible with previous versions of the Load Manager API
The Load Manager API version 8.5 to is not backward compatible with previous versions. Some functions found in previous versions of the Load Manager API may not work in version 8.5.
175739: DTM process generates a core file when you run multiple sessions concurrently
When you run multiple sessions concurrently, the DTM process generates a core file. This does not affect the session results. You can ignore the core file.
175238: Reporting Service gets enabled before all the users and groups in the domain configuration database are synchronized with the Data Analyzer repository
If there are many Data Analyzers users and groups in the domain configuration database, synchronization takes time. The Reporting Service gets enabled on the Administration Console before synchronization completes. If you access the Data Analyzer instance, you might get the following error message: No Privileges.
Workaround: Before accessing the Data Analyzer instance, check the activity log to verify that all users and groups in the Data Analyzer repository have been synchronized with the domain configuration database.
175072: Session with decompress function hangs when you use a Microsoft SQL Server source
Session hangs when the mapping contains a decompress function and reads from a Microsoft SQL Server source.
174889: When you back up a newly upgraded domain configuration database, the backup process fails
If you back up the domain configuration database immediately after you upgrade PowerCenter, the backup process fails.
Workaround: After you upgrade PowerCenter, perform a task that updates the domain configuration, such as creating an application service or adding a user account. After you save the changes to the domain configuration, back up the domain.
173704: Users without adequate permissions cannot create a Reporting Service
If users without adequate permissions to a domain create a Reporting Service in that domain, PowerCenter returns the following error message: “An unexpected error occurred. Contact Informatica Technical Support for assistance.”
Workaround: Verify that users creating the Reporting Service have access permissions to the domain.
171814: Integration Service does not properly recover data for some CDC real-time sessions that write to SQL Server targets
If you recover or warm start a CDC real-time session that writes data to a Microsoft SQL Server target, the Integration Service does not properly retrieve data from the recovery table under the following conditions:
++PowerCenter creates the PM_REC_STATE recovery table in a Microsoft SQL Server database
++The Integration Service connects to an ODBC data source specifying AnsiNPW=no.
Incorrect restart occurs for CDC real-time sessions that use this recovery table.
Workaround: Create the PM_REC_STATE table manually.
170496: You might not be able to connect to the repository during Repository Service
synchronization
You might not be able to connect to the repository in the PowerCenter Client while the Repository Service is synchronizing repository users with LDAP security domain users.
136878: XSD definition contains incorrect code page
When you import an XSD definition with UTF-8 encoding into an ISO-8859-1 repository, and then save and edit it, the encoding changes to Latin 1.
136753: If you import a web service source or target from a WSDL with a large number of elements in hierarchical relationship import mode, the import process can fail
If you import a web service source or target from a WSDL in hierarchical relationship import mode and the Designer generates a large number of XML views in the source or target, the import process fails. The import process can succeed if you import the web service source or target in entity relationship mode.
135022: Links to a port in a target definition fail to import when column name is changed in the target definition
When you change a port name in a target definition and import the definition, mappings with the definition in the target repository do not include a link to the renamed port.
Workaround: Export and import the mapping that includes the target definition.
134614: Internet Explorer may shut down unexpectedly when you configure an LDAP security domain and then move the pointer over the Configure Security icon
Internet Explorer may shutdown unexpectedly when you configure an LDAP security domain and then move the pointer over the Configure Security icon.
Workaround: Apply the latest security updates for Internet Explorer 6.0 or use Firefox to access the Administration Console.
133615: Session fails unexpectedly while running a flat file Lookup transformation
A session fails unexpectedly while running several Lookup transformations. The Lookup transformation that fails is a flat file Lookup transformation that has more than one lookup condition.
The session fails with the following error:
** FATAL ERROR : Unexpected Condition in file [../server/cmnutils/svecmatrix.cpp] line [256]
Workaround: Enable case-sensitive string comparisons.
132253: Integration Service cannot read or write more than 8,000 characters in a text column when it uses an ODBC driver with a Microsoft SQL Server source or target
The Integration Service cannot read more than 8,000 characters from a text column or write more than 8,000 characters to a text column when it uses an ODBC driver to read from or write to Microsoft SQL Server. This problem occurs even if the precision of the source or target column is greater than 8,000.
Workaround: On Windows, use a native database driver instead of an ODBC driver.
131992: Designer shuts down with no errors when you try to use the XML Editor with a large XML schema
The Designer may shut down unexpectedly when you use the XML Editor to open a large XML schema in the Source Analyzer.
Workaround: Do not create XML views when importing the XML source file. Create the views manually in the XML Editor.
130903: Custom profile session fails with fatal error
The DTM process aborts unexpectedly when you run a custom profile session that contains a Custom transformation with 100 or more columns.
130856: Session sometimes fails with an out of virtual memory error when the Integration Service creates a new XML target for each commit
A session sometimes fails with an out of virtual memory error when an XML target is configured to create a new document on commit. When you create an XML document at each commit, the Integration Service allocates virtual memory for each XML root view row. As the Integration Service processes more XML root view rows, the virtual memory buffer requirements increase. The virtual memory allocated is reused across commit intervals. However, if the number of root view rows is large for a commit interval, the session fails and the following error displays:
ERROR: Failed to allocate memory (out of virtual memory). ***********
Workaround: Reduce the number of root view rows for each commit interval or change the mapping to increase the virtual memory available to the Integration Service.
127421: Advanced Purge does not work correctly for source, target, mapplet, and mapping objects
When you preview objects older than the latest version with Advanced Purge, the Designer does not return all of the objects. You cannot purge all of the versioned objects with Advanced Purge.
Workaround: Run a query to retrieve the deleted objects. Select View History. Purge the old object versions by choosing Tools > Purge Object Version.
108493: XML parser performance slows after upgrading to PowerCenter 8.5 on Solaris 32 bit
In PowerCenter 8.5, a session that parses an XML file runs up to 15% slower on Solaris 32bit than in previous versions.
106144: infacmd and infasetup commands hang on sun4v platform
infacmd and infasetup commands hang on machines running on sun4v platform.
105969: Session terminates unexpectedly when the Integration Service tries to set a code page
Session terminates with an unexpected condition when the Integration Service tries to set a code page for a Custom transformation.
104029: DTM process generates a core file when line sequential buffer length is greater than 27,750,000 bytes
When you set the line sequential buffer length great than 27,750,000 bytes, the DTM process generates a core file and the session terminates.
102638: Profile session logs do not appear in the Profile Manager when a persistent profile session fails
You cannot access session logs for failed persistent profile sessions through the Profile Manager.
Workaround: Use the Workflow Monitor to view the session logs.
Data Analyzer Limitations
176319: Data Analyzer displays groups and subgroups of parent or primary groups that are deleted from the User Management Console
Data Analyzer displays subgroups even after the parent or primary group has been deleted. Clicking the user icon associated with that group returns the following error:
Error details: java.lang.RuntimeException: com.informatica.pcsf.common.exception.PCSFConfigException: [UM_10010] The group [Level4-1] belonging to [Native] does not exist in the domain.”
175148: Upgrade does not work if you attempt to upgrade users and groups using the resolution ‘rename to’ with a supplied name that exists in the security domain
If a user or group name is resolved when upgrading users and groups with the resolution ‘rename to’ and the supplied name exists in the selected security domain, the upgrade does not occur.
Workaround: Provide a new name to resolve conflicts or choose to merge the users and groups.
Metadata Manager Limitations
178408: Relationships from packaged models to custom models are deleted during upgrade from 8.5 to 8.5.1
If you create a class-level relationship from a packaged class to a custom class on the Model page, the relationship is removed after upgrade.
178067: Metadata Manager Agent does not start when the installation directory path includes a space
If you install the Metadata Manager Agent and include a space in the installation directory path, the Metadata Manager Agent does not start.
Workaround: Comment out the following line in startup.bat in the
if not "%CATALINA_HOME%" == "" goto gotHome
175479: Permissions on child objects and default permissions on objects in the Metadata Manager catalog are removed during upgrade from 2.2 or 8.1.1 to 8.5.1
If you set permissions on metadata objects in the metadata catalog, the permissions inherited by the child objects are removed when you upgrade the repository. The default permissions set when you create objects are also removed. You must reset the permissions after you upgrade the repository.
174204: You cannot search for multiple tables when you configure an SAP resource on sapr347 and sapr346c machines
When you configure Application Components for SAP, you cannot search for multiple table names separated by commas.
Workaround: Search for single table names.
92040: Data lineage between IBM DB2 CubeViews and a relational database does not work
Data lineage between IBM DB2 CubeViews and a relational database does not work.
Tuesday, May 13, 2008
Photogenic model of the year
Do you want to get recognized, winning a 10,000 USD price or get spotted by an agency for model career ?
http://www.lookoftheyear.com is the answer to your prayers.
Look Of The Year is now looking for people from all over the world to send in their best pictures. So if you are a young model or just a photographer you can use this chance to be the next model working in Paris, New York or Milan.
Join Look of the Year today and start your new life together with beautiful people from all over the world.
Sunday, May 11, 2008
Lifelock new promo codes
Here is what life lock Offers You
1. Proactive Identity Theft Protection
2.. Reduce Junk Mail
3. Reduce Credit Card Offers
4. $1 Million Service Guarantee
5. Only $10 per Month
LifeLock discounts its services by publishing lifelock promo code. Some of these discounts are better than others. The discount available by using PROMO CODE RD17, is as good as it gets. There are no bigger or better discounts available anywhere on the internet other than on lifelock.com.
All you have to do is click on the link above. But while you’re there, read about the services LifeLock provides. LifeLock focuses on prevention; they make it impossible for identity thieves to steal your personal information so you never become a victim. Other companies offer to help their clients clean up after the damage is done.
Click on the link for promo code RD17, and you’re on your way. Or you can do nothing.
Informatica 7 Evaluation Software Download and Install
Step1
Download Informatica eval install software and license keys.
This was not an easy search for me but finally managed to find where the third party software is.Below are the part numbers you need to downloadLogon to edelivery.oracle.com
Download B27745-01 Part 1 of 4 Parts 1 through 4 – Siebel Business Applications. Extract the zip files and you should find the eval software for Informatica. Informatica eval license keys can be found in B27757-01 and B27756-01 documentation.
Once you have downloaded and extracted the zip files, go through setup.exe , make sure to install the Server Components and Client Tools
As discussed in my previous post , Informatica has 4 components to it : Client Tools; Repository Server; Informatica Server and Repository.
At the end of the Install you will have to configure the Repository Server and the Informatica Server.
Configure Repository Server Below:
The following Information needs to be provided:
Server Port Number : 5001 (default can be chosen)
Admin password : enter an Admin Password for the Repos Server
Minimum Port Number
The minimum port number the Repository Server can assign to the Repository Agent process. Default is 5002.
Maximum Port Number
The maximum port number the Repository Server can assign to the Repository Agent process. Default is 65535.
Configuration Directory
The name of the directory in which the Repository Server stores repository configuration information files. You can specify either a relative path or an absolute path. Default is Config.
Backup Directory
The name of the directory in which the Repository Server stores repository backup files. You can specify either a relative path or an absolute path. Default is Backup.
Plugin Directory
The name of the directory in which the Repository Server stores repository plugin files. You can specify either a relative path or an absolute path. Default is Plugin.
Severity Level
The level of error messages written to the Repository Server log. Specify one of the following:
Error. Writes ERROR code messages to the log.
Warning. Writes WARNING and ERROR code messages to the log.
Information. Writes INFO, WARNING, and ERROR code messages to the log.
Tracing. Writes TRACE, INFO, WARNING, and ERROR code messages to the log.
Debug. Writes DEBUG, TRACE, INFO, WARNING, and ERROR code messages to the log.
Output to Event Log
Enable this option if you want to write Repository Server messages to the Windows Event Log. This option is enabled by default.
Output to File
Enable this option if you want to write Repository Server log messages to a file. When you enable this option, enter a file name for the Repository Server log. This option is disabled by default. The default Repository Server log file name is pmrepserver.log. The Repository Server stores the Repository Server log file in the Repository Server installation directory.
Configure Informatica Server (PowereCenter Server) as a Service:
Information that needs to be provided is as below:
Server Tab:
Server Name: The name of the PowerCenter Server to register with the repository. This name must be unique to the repository. This name must also match the name you specify when you use the Workflow Manager to register the PowerCenter Server.
TCP/IP Host Address: The TCP/IP host address as an IP number (such as 123.456.789.1), or a local host name (such as RECDB), or a fully qualified name (such as RECDB.INVOICE.COM). If you leave this field blank, the PowerCenter Server uses the default local host address.
Max No. of Concurrent Sessions: The maximum number of sessions the PowerCenter Server runs at a time. Increase this value only if you have sufficient shared memory. Default is 10.
Shared Memory: The amount of shared memory available for use by the PowerCenter Server Load Manager process. For every 10 sessions in Max Sessions, you need at least 2,000,000 bytes reserved in Load Manager Shared Memory. Default is 2,000,000 bytes.
Error Severity Level for Log Files: The level of error messages written to the PowerCenter Server log. Specify one of the following message levels:
Error. Writes ERROR code messages to the log.
Warning. Writes WARNING and ERROR code messages to the log.
Information. Writes INFO, WARNING, and ERROR code messages to the log.
Tracing. Writes TRACE, INFO, WARNING, and ERROR code messages to the log. Debug. Writes DEBUG, TRACE, INFO, WARNING, and ERROR code messages to the log.
Fail Session if Maximum Number of Concurrent Sessions Reached: Enable this option if you want the PowerCenter Server to fail the session if the number of sessions already running is equal to the value configured for Maximum Number of Concurrent Sessions. If you disable this option, the PowerCenter Server places the session in a ready queue until a session slot becomes available. This option is disabled by default.
Allow mapping/session debugging: If selected, you can run the Debugger. This option is enabled by default.
Time Stamp Workflow Log: Enable this option if you want to append a time stamp to messages written to the workflow log. This option is disabled by default.
Output to Event Log: Enable this option if you want to write PowerCenter Server messages to the Windows Event Log. This option is enabled by default.
Output to File: Enable this option if you want to write PowerCenter Server log messages to a file. When you enable this option, enter a file name for the PowerCenter Server log.
Repository Tab:
Repository Name : The name of the repository to connect to. You create a repository in the Repository Server Administration Console.
Repository User: The account used to access the repository. When you first create a repository, the Repository User is the database username. You create other Repository Users in the Repository Manager.
Repository Password : The password for the Repository User. When you first create a repository, the password is the password for the database user.
Repository Server Host Name: The name of the machine hosting the Repository Server.
Repository Server Port Number: The port number the Repository Server uses to communicate with repository client applications.
Repository Server Timeout: The maximum number of seconds that the PowerCenter Server tries to establish a connection to the Repository Server. If the PowerCenter Server is unable to connect to the Repository Server in the time specified, the PowerCenter Server shuts down. Default is 60 seconds.
Licenses Tab:
Enter the license Key’s and then click update
Compatibility and Database Tab:
PMServer 3.X aggregate compatibility: If selected, the PowerCenter Server handles Aggregator transformations as it did in PowerMart 3.x. This overrides both Aggregate treat nulls as zero and Aggregate treat rows as insert.
If you select this option, the PowerCenter Server treats nulls as zeros in aggregate calculations and performs aggregate calculations before flagging records for insert, update, delete, or reject in Update Strategy expressions. If you do not select this option, the PowerCenter Server treats nulls as nulls and performs aggregate calculations based on the Update Strategy transformation.
PMServer 6.X Joiner source order compatibility: If selected, the PowerCenter Server processes master and detail pipelines sequentially as it did in versions prior to 7.0. The PowerCenter Server processes all data from the master pipeline before starting to process the detail pipeline. Also, if you enable this option, you cannot specify the Transaction level transformation scope for Joiner transformations. If you do not select this option, the PowerCenter Server processes the master and detail pipelines concurrently.
Aggregate Treat Nulls as Zero: If selected, the PowerCenter Server treats nulls as zero in Aggregator transformations. If you do not select this option, the PowerCenter Server treats nulls as nulls in aggregate calculations.
Aggregate Treat Rows as Insert : If selected, the PowerCenter Server performs aggregate calculations before flagging records for insert, update, delete, or reject in Update Strategy expressions. If you do not select this option, the PowerCenter Server performs aggregate calculations based on the Update Strategy transformation.
PMServer 4.0 date handling compatibility: If selected, the PowerCenter Server handles dates as in PowerCenter 1.0/PowerMart 4.0. Date handling significantly improved in PowerCenter 1.5 and PowerMart 4.5. If you need to revert to PowerCenter 1.0 or PowerMart 4.0 behavior, you can configure the PowerCenter Server to handle dates as in PowerCenter 1.0 and PowerMart 4.0.
Treat CHAR as CHAR on Read: If you have PowerCenter Connect for PeopleSoft, you can use this option for PeopleSoft sources on Oracle. You cannot, however, use it for PeopleSoft lookup tables on Oracle or PeopleSoft sources on Microsoft SQL Server.
Max LKP/SP DB Connections: Allows you to specify a maximum number of connections to a lookup or stored procedure database when you start a workflow. If the number of connections needed exceeds this value, session threads must share connections. This can result in a performance loss. If you do not specify a value, the PowerCenter Server allows an unlimited number of connections to the lookup or stored procedure database.
If the PowerCenter Server allows an unlimited number of connections, but the database user does not have permission for the number of connections required by the session, the session fails. A default value is not specified.
Max Sybase Connections: Allows you to specify a maximum number of connections to a Sybase database when you start a session. If the number of connections required by the session is greater than this value, the session fails. Default is 100.
Max MSSQL Connections: Allows you to specify a maximum number of connections to a Microsoft SQL Server database when you start a workflow. If the number of connections required by the workflow is greater than this value, the workflow fails. Default is 100.
Number of Deadlock Retries: Allows you to specify the number of times the PowerCenter Server retries a target write on a database deadlock. Default is 10.
Deadlock Sleep Before Retry (seconds): Allows you to specify the number of seconds before the PowerCenter Server retries a target write on database deadlock. Default is 0 and the PowerCenter Server retries the target write immediately.
Configuration Tab
Data Movement Mode: Choose ASCII or Unicode. The default data movement mode is ASCII, which passes 7-bit ASCII character data. To pass 8-bit ASCII and multibyte character data from sources to targets, use Unicode mode.
Validate Data Code Pages: If you enable this option, the PowerCenter Server enforces data code page compatibility. If you disable this option, the PowerCenter Server lifts restrictions for source and target data code page selection, stored procedure and lookup database code page selection, and session sort order selection. This option is only available when the PowerCenter Server runs in Unicode data movement mode. By default, this option is enabled.
Output Session Log In UTF8: If you enable this option, the PowerCenter Server writes to the session log using the UTF-8 character set. If you disable this option, the PowerCenter Server writes to the session log using the PowerCenter Server code page. This option is available when the PowerCenter Server runs in Unicode data movement mode. By default, this option is disabled.
Warn About Duplicate XML Rows: If you enable this option, the PowerCenter Server writes duplicate row warnings and duplicate rows for XML targets to the session log. By default, this option is enabled.
Create Indicator Files for Target Flat File Output: If you enable this option, the PowerCenter Server creates indicator files when you run a session with a flat file target.
Output Metadata for Flat File Target: If you enable this option, the PowerCenter Server writes column headers to flat file targets. It writes the target definition port names to the flat file target in the first line, starting with the # symbol. By default, this option is disabled.
Treat Database Partitioning As Pass Through: If you enable this option, the PowerCenter Server uses pass-through partitioning for non-DB2 targets when the partition type is Database Partitioning. Enable this option if you specify Database Partitioning for a non-DB2 target. Otherwise, the PowerCenter Server fails the session.
Export Session Log Lib Name: If you want the PowerCenter Server to write session log messages to an external library, enter the name of the library file.
Treat Null In Comparison Operators As: Determines how the PowerCenter Server evaluates null values in comparison operations. Enable one of the following options:
a)Null. The PowerCenter Server evaluates null values as null in comparison expressions. If either operand is null, the result is null. This is the default behavior.
b)High. The PowerCenter Server evaluates null values as greater than non-null values in comparison expressions. If both operands are null, the PowerCenter Server evaluates them as equal. When you choose High, comparison expressions never result in null.
c)Low. The PowerCenter Server evaluates null values as less than non-null values in comparison expressions. If both operands are null, the PowerCenter Server treats them as equal. When you choose Low, comparison expressions never result in null.
WriterWaitTimeOut: In target-based commit mode, the amount of time in seconds the writer remains idle before it issues a commit when the following conditions are true:
a)The PowerCenter Server has written data to the target.
b)The PowerCenter Server has not issued a committed.
The PowerCenter Server may commit to the target before or after the configured commit interval. Default is 60 seconds. If you configure the timeout to be 0 or a negative number, the PowerCenter Server defaults to 60 seconds.
Microsoft Exchange Profile: Microsoft Exchange profile used by the Service Start Account to send post-session email. The Service Start Account must be set up as a Domain account to use this feature.
Date Display Format: If specified, the PowerCenter Server validates the date display format and uses it in session log and server log entries. If the date display format is invalid, the PowerCenter Server uses the default date display format. The default date display format is DY MON DD HH 24:MI:SS YYYY. When you specify a date display format, it displays in the test window. An invalid date display format is marked invalid.
Test Formatted Date: Read-only field that displays the current date using the format selected in the Date Display Format field.
JVM Options Tab:
You can configure JVM options if you run Java-based programs with PowerCenter Connect products, such as PowerCenter Connect for JMS or PowerCenter Connect for webMethods.
HTTP Proxy Tab:
Server Name: Name of the HTTP proxy server.
Server Port: Port number of the HTTP proxy server.
Username: Authenticated user name for the HTTP proxy server. This is required if the proxy server requires authentication.
Password: Password for the authenticated user. This is required if the proxy server requires authentication.
Domain: Domain for authentication.
Once you have completed configuring the Repository Server and Power Center Server – Login to the Repository Server Admin Console and create a new Repository
Once the Repository is created (to create the repository a repository schema needs to be created in the database server); the Repository owner information can be used to Login to Designer, Workflow Manager and Workflow Monitor.
LifeLock now offers protection for kids
According to lifelock reviews by consumers, the identities of children are now being stolen by thousands. They are easy targets because no one ever monitors them. These kids aren't finding out until they graduate from high school and apply for their first job or a student loan. By then, thieves have often been using their Identities for years and the kid's good name is ruined before he or she even has a chance to start.
This service comes with $1 million guarantee. The process is tailored to be most effective for the special requirements needed to protect your child's Identity.
If you signup using lifelock promo code, you get credit reports checks every 6 months to ensure that there is no activity.
If a credit report does exist, they place fraud alerts on credit reports, stating that this is a minor child and that no activity should occur.
LifeLock checks for work history and any misuse of the Social Security number and repeat this process regularly to ensure that all is well.
Starting out is hard enough. Starting out with a stolen Identity makes it ten times harder. We think that's worth $25 a year. Do you?
Monday, May 5, 2008
Comparing Informatica and OWB
One major difference is that OWB will only populate Oracle 8i, 9i or 10g data warehouses, whilst Informatica works against any major vendor (thanks Duncan for pointing that one out, one of those ’so obvious if you’re used to OWB, I forgot to mention it’ moments…)
Both tools allow you to built reusable components for transforming data, with Powercenter’s being specific to the tool whilst Oracle’s are regular PL/SQL functions and procedures. Informatica, like Oracle, are making a big noise
about grid computing. "PC7 offers server grid capabilities, too, by which
PowerCenter can distribute loads across heterogeneous Unix, Windows, or
Linux-based computing platforms. Although grid capabilities may seem exciting,
I don’t believe they match real-world need for grid computing yet, and I
wouldn’t recommend using them in place of other industry grid solutions."
The main architectural different between Powercenter and OWB is that Powercenter has it’s own ETL engine, that sits on top of the source and target databases and does it’s own data movement and transformation, whilst OWB uses SQL and the built-in ETL functions in 9i and 10g to move and transform data. Interestingly the article observes that the Informatica approach can be slower than the approach used with OWB. "Also, be aware that ETL tools are in general a slower (if more elegant) alternative to native SQL processing (such as Oracle PL*SQL or Microsoft Transact SQL)."
Powercenter’s use of web services and distributed computing looks more developed than OWB’s. "PowerCenter Web services are managed through the Web Services Hub, another component of the architecture, which supports standards such as Simple
Object Access Protocol (SOAP), Web Services Description Language (WSDL), and Universal Description, Discovery, and Integration (UDDI). The architectural components can be collocated on a single server or spread across diverse servers, which allows solution parallelism, flexibility, and scalability."
Powercenter starts at around $200,000 (yikes!) although there is a "Flexible pricing model.". OWB is licensed as part of 10gDS which is around $5000 per named user, although you’ll need the Enterprise Edition of the 8i, 9i or 10g database to provide the ETL functionality.
Sunday, May 4, 2008
lifelock keeps identity thieves at bay during the 2008 tax season
These “phishing” schemes can take a variety of forms, the most common of which involves an identity thief who calls or e-mails a consumer pretending to be an IRS employee. The consumer is promised a sizable rebate if they file their taxes early. All the caller needs in exchange is the consumer’s bank account number to deposit the check.
The bad news is that schemes like the one described above are common; the good news is that falling victim to one is avoidable – as long as consumers get smart on the facts and follow the proper precautions laid out by lifelock, America's #1 Identity theft prevention program, you are ensured total safety and guarantee of your identity up to $1,000,000.
lifelock.com offers some important advice that every consumer should know about protecting their personal information during tax season. When you signup using lifelock promotion code you are ensured that a highly-skilled team that includes veteran licensed investigators are on your side. They review IRS alerts to stay apprised of emergent tax fraud issues – bolstering with specialized work sof upporting breach victims and restoring individuals’ compromised identities to pre-theft status.
lifelock promo code now all over the internet
The advantages of using lifelock promo code are:
1. Unlimited access to all 3 credit scores
2. I.D. Theft Expense Reinbursement Coverage:
3. Credit analysis tools
4. Upgrades to 3-in-1 credit reports with 3 credit scores from all 3 bureaus at no additional cost
5. Easy to ready report
6. Good frequency of credit alerts whenever certain changes are detected (via e-mail, phone, mail or text messaging)
7. Unlimited access to all 3 credit reports and scores
8. Credit alerts on
- new accounts
- credit inquiries
- address changes
- public records
- changes to current accounts
Take a look and see if this solution meet your needs. To receive the best discount available use promotion code RD32.
Life Lock keeps your identity safe
1. You get a phone call or letter telling you that you have been approved or denied credit for accounts that you never requested.
2. You no longer receive your credit card statements, or you notice that some of your mail seems to be missing.
3. Your credit card statement includes charges for things you know you never bought.
4. A collection agency tells you they are collecting for an account you never opened.
If you notice anything like this, it's possible you've become a victim of identity theft. But what if nothing is obviously wrong? How can you be sure you're not a victim? According to the U.S. Federal Trade Commission, it takes 12 months, on average, for a victim of identity theft to notice the crime. You don't want to let 12 months go by before finding that you're a victim. Here is where Life Lock comes into picture. Be Sure You're Not a Victim. Check Your Credit Report on LifeLock.
The Federal Trade Commision says "One of the best ways to catch identity theft is to regularly check your credit record." When anyone applies for credit in your name, it will show up in your credit report. You just need to figure out where to get your credit report and how often to get it. Credit Monitoring is another option to safeguard your credit history that you built over so many years. LifeLock reviews proves that it is the best credit monitoring products out there. Take a look and see if any of them meet your needs. LifeLock will guarantee your identity up to $1,000,000. LifeLock is America's #1 Identity theft prevention program. To receive the best discount available use promotion code RD32