The customer historically had Siebel Remote disabled through setting the Docking Transaction Logging System Preference to FALSE but had recently added a number of mobile users to the Enterprise. They re-enabled transaction logging within the Enterprise by setting the parameter to TRUE but having done this noted that none of the transactions which were being logged within the Enterprise were being sent out to the userbase.
The first step in this scenario was to make a review of the log files being produced by the two components involved in the routing of transactions, the Transaction Processor and Transaction Router. When a review of the Transaction Processor log was made it was identified that the component was repeatedly issuing DELETE statements against the master transaction log table (S_DOCK_TXN_LOG) :
SQL SQL 4 2003
SQL SQL 4 2003
delete from dbo.S_DOCK_TXN_LOG
where TXN_ID = {fn convert(?, SQL_NUMERIC)}
SQL SQL 4 2003
SQL SQL 4 2003
[SQL01] Total Rows: 1 Total Time Parse: 0s Execute: 0s Avg Time: 0s
SQL SQL 4 2003
After examining this statement and the various routing details available through the Siebel Remote Administration screens it was identified that the transactions which were being generated by the Enterprise had a lower TXN_ID than those which had historically been routed. The Transaction Processor maintains a 'LOWSCANMARK' value which indicates the earliest TXN_ID value which is needed by the Enterprise and therefore deletes anything below this value. When new transactions are generated the system sets the TXN_ID to the next value from an object which differs for various databases. In the case of Oracle the TXN_ID is generated from a sequence object S_DOCK_TXN_LOG_S, whilst in the case of Microsoft SQL Server and DB2 the TXN_ID is based on an IDENTITY column.
At some point in time the TXN_ID column's value (created automatically on Insert as this was a Microsoft SQL Server environment and therefore an IDENTITY column) had been reset leading to new transactions having a value below the LOWSCANMARK. These were therefore removed immediately by the Transaction Processor.
In order to resolve this behavior it was necessary to reset the value of the TXN_ID column. This process differs for each database management system. In this case it was necesary to reset the IDENTITY column to a value higher than the LOWSCANMARK.
Please run the following query to determine the LOWSCANMARK values for Transaction Processors in your Siebel Enterprise :
select n.name, ds.NODE_ID "Processor node id", substr(addtl_info, 1, 50) "Low Scan Mark Value" from s_dock_status ds, s_node n
where ds.type='ROUTE'
and ds.local_flg='Y'
and ds.node_id = n.row_id
and n.node_type_cd='TXNPROC';
Having identified the LOWSCANMARKS please ensure that the
1) Have all of the mobile clients synchronize with the Server to download any outstanding transactions
2) Wait until all %SIEBEL_SERVER_ROOT%\DOCKING\
3) Shutdown the Siebel Enterprise to ensure that new data is not written into the transaction log
4) Run a DBCC CHECKIDENT(S_DOCK_TXN_LOG
5) Run a DBCC CHECKIDENT(S_DOCK_TXN_LOG
6) Restart the Siebel Enterprise but at the moment restrict login to yourself
7) Re-extract the mobile users
8) Have them initialize and pickup the new extract
9) Check that newly created transactions in S_DOCK_TXN_LOG have a TXN_ID of >=
10) Enterprise should then be fully available.
"We seem to have an overabundance of people nowadays who have a high sense of entitlement - that somebody else, the government, i.e., we taxpayers, owe them. Whenever a tax cut is announced, they come out of the woodwork complaining about the "rich getting richer". We just need to remind them of the parable of the talents. The one that buried his talent was called slothful and wicked. His talent was taken away from him and given to the one that had ten (the "richest" one, so to speak). Jesus did not say it directly, but the implication in that parable is that he sided with the industrious ones and chided the slothful, fearful one.
Anyway this is a great explanation of our tax system.
Sometimes politicians, journalists and others exclaim; "It's just a tax cut for the rich!" and it is just accepted to be fact, without questioning it. But what does that really mean?
Just in case you are not completely clear on this issue, the following might help. Let's put tax cuts in terms everyone can understand.
Suppose that every day, ten men go out for beer and the bill for all ten comes to $100. If they paid their bill the way we pay our taxes, it would go something like this:
The first four men (the poorest) would pay nothing.
The fifth would pay $1.
The sixth would pay $3.
The seventh would pay $7.
The eighth would pay $12.
The ninth would pay $18.
The tenth man (the richest) would pay $59.
So, that's what they decided to do.
The ten men drank in the bar every day and seemed quite happy with the arrangement, until on day, the owner threw them a curve. "Since you are all such good customers," he said, "I'm going to reduce the cost of your daily beer by $20."Drinks for the ten now cost just $80.
The group still wanted to pay their bill the way we pay our taxes so the first four men were unaffected. They would still drink for free. But what about the other six men - the paying customers? How could they divide the $20 windfall so that everyone would get his 'fair share?' They realized that $20 divided by six is $3.33. But if they subtracted that from everybody's share, then the fifth man and the sixth man would each end up being paid to drink his beer. So, the bar owner suggested that it would be fair to reduce each man's bill by roughly the same amount, and he proceeded to work out the amounts each should pay.
And so:
The fifth man, like the first four, now paid nothing (100% savings).
The sixth now paid $2 instead of $3 (33%savings).
The seventh now pay $5 instead of $7 (28%savings).
The eighth now paid $9 instead of $12 (25% savings).
The ninth now paid $14 instead of $18 (22% savings).
The tenth now paid $49 instead of $59 (16% savings).
Each of the six was better off than before. And the first four continued to drink for free. But once outside the restaurant, the men began to compare their savings."I only got a dollar out of the $20,"declared the sixth man. He pointed to the tenth man," but he got $10!" "Yeah, that's right," exclaimed the fifth man. "I only saved a dollar, too. It's unfair that he got ten times more than I!" "That's true!!" shouted the seventh man. "Why should he get $10 back when I got only two? The wealthy get all the breaks!" "Wait a minute," yelled the first four men in unison. "We didn't get anything at all. The system exploits the poor!"
The nine men surrounded the tenth and beat him up.
The next night the tenth man didn't show up for drinks, so the nine sat down and had beers without him. But when it came time to pay the bill, they discovered something important. They didn't have enough money between all of them for even half of the bill!
And that, boys and girls, journalists and college professors, is how our tax system works. The people who pay the highest taxes get the most benefit from a tax reduction. Tax them too much, attack them for being wealthy, and they just may not show up anymore. In fact, they might start drinking overseas where the atmosphere is somewhat friendlier."
Women: Learn your place. Review this educational video for more training. Please share with a friend, you know you'd want them to do the same for you.














*Keep in mind that each time someone replies to a message you send using a custom 'From:' address, the reply will be delivered to the 'From:' address rather than your Gmail address. If you'd like replies to be delivered to another account, you'll need to enter a 'reply-to' address. Just click Specify a different reply-to address to enter this information.
NEXT, you'll want to set up a filter. This is a piece that Google doesn't tell you about. Since you are going to leave the email in your other accounts, you will want to be able to easily identify and delete email from those account that is in your main Gmail (aggregate) account. That way, you don't fill up your main gmail account.
Here's the Google Help instructions on setting up a filter. Read after for my recommendations. The orginal help is at: http://mail.google.com/support/bin/answer.py?answer=6579
Gmail's filters allow you to manage the flow of incoming messages. Using filters, you can automatically label, archive, delete, star, or forward your mail, based on any combination of keywords, sender, recipients, and more.
To create a filter:
To edit or delete existing filters:
MY RECOMMENDATION is that the Filter criteria is on the "To:" you should set that to one of the addresses in your "send mail as." Then, as the action, apply a label. The Label can be the email address as well. Keep it simple.
Consider doing the same with your POP Accounts. As a last little tip, if you want to aggregate your Yahoo and Hotmail accounts, simply set them to be checked via POP!
Enjoy
PREHEAT oven to 375°F. Brown meat in large skillet on medium heat; drain. Return meat to skillet. Add onions and peppers; cook until crisp-tender, stirring occasionally. Add salsa, corn and seasonings; mix well.
LAYER one third of the meat mixture and one half each of the tortillas and cottage cheese in 13x9-inch baking dish. Repeat layers; cover with remaining meat sauce. Sprinkle with Cheddar cheese and olives.
BAKE 30 min. or until heated through.
Start with your hips right over the stability ball. With one toe down, extend your left hand up, keeping your right fingertip palm down, while lifting your right leg up. Hold for a count of three and then switch sides. Continue for 3 sets of 10, taking thirty to sixty seconds in between each set.
Start with your stomach on top of the ball and you knees on the mat. You will want to fall forward over the ball in a relaxed position. From there you will come up to the point where your back feels as though it is parallel with the ball. Your hands and arms should be raised and come straight out so they are also parallel with the ball. Hold this position for a count of 5. Continue for a set of 10.
Sitting on the ball, with your feet flat on the mat, square yourself your spine is perfectly straight. Take a weight in your right hand, drop that hand behind your head and use your left hand as a brace to keep your elbow right beside you head. Pivot around your elbow joint lifting your right hand above your head, as you squeeze the back of your arm. Then lower back down. You will want to switch between arms as you continue for 3 sets of 10 on each side.
Working with lighter weights, start by sitting on the ball and then bend over so that your back becomes like a table and you can wrap your arms around the middle of your thighs. Pick up the light hand weights and put them on your hands. You should have soft elbows but almost an extended arm. Bring you arms straight up and to your sides, so that they are almost parallel with the ground. Then bring them back down.
An alternative to the light weights is no weight at all. You will want to continue this exercise for 3 sets of 10.
This exercise is very similar to the bent-over raise. Working with light weights in a standing position bring the weights straight up and to your sides. You will want to point your little finger towards the ceiling. Be sure to keep you back straight the entire time and bring your arms up so that they are parallel to the ground. Continue for 3 sets of 10.
From a standing position, start with your arms down in front of you, your palms should be facing your legs with your weights in your hands. Begin by pulling your arms straight up your body so that your elbows are a little higher than your hands. Then bring your hands back down. It is important to emphasis a pause at the bottom. Continue for 3 sets of 10.
I like to tell people that Liege Waffles are basically the Belgian donut. They are hand-held, sweet, require no syrup, and are good hot or cold. They're more dense than their cousin from Brussels, and frankly, I like them better. Cook them at night for an easy desert, and save the rest for breakfast as you walk out the door or when you get to the office.FAQ 2256: How Can You Disable the Automatic Trailing Wildcard in a Query?