What did Christ accomplish in dying on the cross, and for whom?
The rather obvious reason for a treatment of this subject at this time is that through Professor Harold Dekker's writings in the Reformed Journal it has become a pertinent issue. Prof. Dekker holds to the proposition that God loves all men. He maintains, further, that there is only one love of God, and that this one love of God is redemptive, though, strange to say, he does not maintain that it is redeeming. In this connection, it naturally follows that he must say something about the atoning death of Christ. And his position on this score is that the atonement of Christ is unlimited, universal, for all men. At this point Dekker makes a four-fold distinction. He teaches that the atonement is unlimited in three senses, namely, in respect to its sufficiency, in respect to its availability, and in respect to the divine desire. In one respect the atonement is limited to the elect, namely, as to its saving efficacy.
My second reason for treating this particular subject is that Prof. Dekker has maintained that his position on the atonement is the position of the Canons of Dordrecht. He has appealed especially to Canons II, 8, claiming that this article proves that Dordt dealt only with the question of the 'efficacious application of saving grace,' and in no other sense dealt with the question of the design of the atonement (cf. The Reformed Journal, December 1962, pp. 6-7). This, of course, is only a very limited aspect of Dekker's whole position. But for more than one reason it is also a very integral aspect of his stand. It concerns the question whether Prof. Dekker's explanation of the atonement is confessionally Reformed or not. To this specific question we will devote our attention in the present essay.
For clarity's sake, I will immediately set forth my own position in regard to this fundamental issue, a position which I hope to prove in this essay. My position is that the only atonement of which Dordt knows and for which it leaves room is an efficacious one, both as far as its redemptive (and redeeming) character is concerned, and as far as its application and appropriation is concerned. This was precisely the issue in the conflict with the Arminians which was decided at Dordrecht. The question was: is the atonement of Christ effectual both objectively (as far as its merit goes) and subjectively (as far as its application goes), or is it ineffectual—in which case it is not atonement or redemption at all? The former is the Reformed position; the latter was the Arminian. Dordt knew only of a limited and effectual atonement, for the elect alone. If the Arminian position of a real atonement for all men is correct, then the Arminian must be a thorough-going universalist and must maintain too that all men are actually saved. The only way out of this dilemma is to deny the objective reality of atonement in the death of Christ, to empty that death of Christ of its real atoning significance. The latter is precisely what the Arminians did, or tried to do, in several ways while they continued to speak of Christ's death and Christ's atonement in the usual terms. And I maintain, and hope to show, that this is precisely what Prof. Dekker's position compels him to do in his four-fold distinction of sufficiency, availability, desire, and efficacy. The Canons condemn any such atonement in any universal sense; and they allow no room for Dekker's theory.
1) What do the Canons themselves say of the atonement?
2) What light, if any, do the opinions of the various delegates to the Synod of Dordrecht (both Dutch and foreign) shed on Dordt's understanding of the atonement?
3) Can Prof. Dekker's three-fold universal atonement stand in the light of Dordt?
Here, therefore, the Arminians teach: 1) That the atonement of Christ is for every individual, so that Christ obtained reconciliation and forgiveness of sins for them all. 2) Yet that this atonement is effectual only in the believers. And the Arminians would even say that it is effectual only in the elect, although they did not like to use that term too much. In Article 3 of the Remonstrance they even say that man does not have saving faith of himself, though they add in Article 4 that the grace that bestows saving faith is not irresistible. Later on, of course, the Arminians were forced to develop their position, because they could not explain ultimately why all men were not reconciled and forgiven if Christ actually obtained reconciliation and forgiveness for all. The result was that in various ways—some of which are described and condemned in Canons II, Rejection of Errors—they began to deny the real atoning character of the death of Christ and to get rid of such elements as satisfaction, substitution, redemption, etc. One of the most notorious attempts at this was Hugo de Groot's [Grotius’] governmental theory, which made of the death of Christ a divine demonstration of what God could justly do to all men on account of their sins, a demonstration designed to make men acknowledge God's righteousness and repent, and thus be saved.
But we must keep the two main elements of Article 2 of the Arminians in mind. This is the view which our Canons condemn; and they condemn it on both counts. If Prof. Dekker's explanation of Canons II is correct, the Arminians and the Reformed would have been in agreement as far as the atonement was concerned: a death of Christ for all, but efficacious only in the believers, that is, the elect. And notice also the striking similarity between Dekker's and the Remonstrants' citing of passages like John 3:16 and 1 John 2:2.
1) That atonement is a matter of strictest divine justice (Art. 1). That justice means that God blesses and gives life to the righteous, i.e., to those who are one hundred per cent in harmony with the standard of His own righteousness, His law, 'Thou shalt love me.' He curses and punishes those who break that law with temporal and eternal punishment, both in body and soul. Sin, therefore, is guilt. It is debt, liability to punishment.
2) The punishment demanded by God's justice cannot be escaped, and man cannot be restored to God's favor, unless satisfaction is made. Here we have a key word in the understanding of atonement: satisfaction. It means to do enough, to make payment of a certain debt or obligation, according to the demand of justice. (The Dutch is: voldoening, genoegdoening.) The reader should keep this term in mind because it denotes a very exact relationship. If satisfaction of a debt of one thousand dollars is made for a man, that debt is no more! If satisfaction of the debt of sin is made in any real sense for all men, that debt is no more! And remember: if Christ died His atoning death for all men, then He satisfied for all men!
a) This satisfaction, payment of debt, we are unable to make in our own persons, and therefore we are unable to deliver ourselves (Art. 2).
b) God's only begotten Son made this satisfaction for us and in our stead. He was made sin and became a curse. This death of the Son of God is the only and most perfect sacrifice and satisfaction for sin, for it is of infinite value and worth (Art. 2 and 3).
c) This satisfaction is, therefore, a matter of substitution. It is for us, in our behalf, for our benefit, in the sense that is in our stead. Here you have a second key idea: substitution. Our Lord Jesus Christ represented men legally, took their place, before the bar of God's justice. Whether that was all men or only the elect is not now the question; but He represented men, substituted for them. He was their Head. This is a very exact relationship. If one man substitutes and satisfies for the debt of one thousand men, the debt of those one thousand (not of five thousand others) is paid and cannot be held against them. If Christ died, substituted and satisfied, for the elect only, then their debt (not the debt of all the others) is paid: it cannot be held against them. If, on the other hand, He died for an, then the debt of all is paid: it cannot be held against them, they are forgiven and saved.
6) Article 6 does not even by implication speak of a sufficiency of Christ's death for all. It speaks rather of the guilt, blame, of unbelief. That men go lost is not to be blamed to Christ's sacrifice being defective, but it is to be blamed to men themselves. We should remember, by the way, that the Arminians accused the Reformed of teaching that Christ's sacrifice was defective, i.e., it wasn't big enough to save all men, and that this was proved by some going lost because they were not covered by it. The Reformed answered: 'No, that men go lost is to be blamed on their own unbelief, not on Christ.' But the Arminians, even with their universal atonement, really taught that Christ's sacrifice was defective: for they taught that the sacrifice of Christ covered all the sin of all men except the sin of unbelief and impenitence.
7) Article 7 stresses that those who are saved through the death of Christ are indebted for this benefit solely to God's grace, not to any merit of their own. Hence, those who are lost go lost through their own fault; those who are saved are not saved through their own merit.
8) And now we come to Article 8, which Prof. Dekker cited in claimed support of his view. Let us analyze this article carefully.
b) This main proposition the article distinguishes into two aspects.
This is the objective redemption, purchase, justification of all the elect in the cross. Christ represented all the elect, those dead, those living, those yet to be born, at the cross. From the moment that He died for them all their debt was very really paid and removed before God. They are from that moment righteous. God, according to His justice, can never demand payment for their sins any more; but He must and does hold them righteous, and account them worthy of eternal life.
This is the subjective side of salvation. It speaks of the work of Christ in us. And it is explained in detail in the rest of the Canons (III/IV, and V). By this we come into actual, conscious possession of all the blessings of salvation. Moreover, this is grounded in the work of Christ for us, objective redemption, by which Christ 'purchased' these benefits for us. Also this effectual application is for the elect alone. In conclusion, therefore, Article 8 insists that the atonement (objective redemption, substitutionary satisfaction) is effectual and for the elect alone. It actually purchases something for the elect, so that they have the right to it. And the application of the benefits of the atonement is effectual and for the elect alone, so that the latter actually come into possession of all the purchased benefits. The two aspects are co-extensive: they both extend to the elect alone.
In the light of all this we ask the question: does Canons II allow any room for any other atonement than an efficacious atonement for the elect alone? The answer has to be NO! As soon as you understand that atonement is satisfaction and is vicarious, substitutionary satisfaction, you are shut up to the view that the atonement is strictly limited to the elect, or you must maintain that if Christ died for all men, then all men are surely saved. The former is the position of Canons II, 8; the latter is the position of Arminianism, except that it denies that atonement is effectual.
We may also ask: does Canons II at all condemn any other view of the atonement, any view which attempts to make atonement general? Yes, they do, in the Rejection of Errors. In Article 1 they expressly condemn the view of an ineffectual redemption, when they condemn the idea that the merit of Christ's death was general and indefinite, while it might never have been applied to anyone at all. In Article 3 they reject the view that Christ satisfied, but did not merit either salvation or faith for anyone. And in Article 6 they condemn a view that sounds like Prof. Dekker's teaching concerning the divine desire in the death of Christ, namely, that “God, as far as he is concerned, has been minded of applying to all equally the benefits gained by the death of Christ.' The reader should look up these articles.
But, finally, do not the Canons make a kind of general statement concerning Christ's death? Indeed they do, in II, 3 they state that Christ's death is “of infinite worth and value, abundantly sufficient to expiate the sins of the whole world.' But we should note the following in this connection: 1) The Canons carefully use the word 'sufficient,' not 'satisfying.' The Dutch here is “genoegzaam;' and the Latin, “sufficiens.' 2) The Canons nowhere state that Christ actually died for all, or substituted for all, or satisfied for all, or redeemed all. In fact, this is the very error against which the Canons militate. 3) In this article and this expression the Canons are not concerned with the question for whom Christ died, but with the Arminian argument that the Reformed view of limited atonement presupposes that the sacrifice of Christ was too poor and of limited value. From this point of view they, as it were, answer: “Oh, no; apart from the fact that Christ did not die for all, that death of Christ in itself is so worthy and valuable that if God had so willed, it would have very well covered the sins of the whole world. From that point of view it was abundantly sufficient.' 4) The Canons never say: 'for all men and every man.' 5) We gladly concede that this approach of the Canons is abstract and philosophically speculative. The approach of Article 4 is much sounder and is scriptural, when it comes to the value and worth of Christ's sacrifice. 6) This interpretation of Article 3 is supported by the official opinions of the delegations to the Synod, as we shall see.
That the above is indeed the position of our Canons and that the propositions of Prof. Dekker are contrary to the whole spirit of Dordt can be abundantly proved from the writings of the very fathers who composed the Canons. Fortunately, these writings are preserved in the Acts of the Synod of Dordrecht. The Acts contain not only the official decisions of the Synod, but also the written opinions of each delegation to the Synod, both of the delegations from foreign countries and of the delegations from the various Dutch provinces. These lengthy reports contain a detailed treatment of each of the Five Articles of the Arminians. In my Dutch version of the Acts of the Synod of Dordrecht the opinions on the subject of the atoning death of Christ alone cover more than a hundred large pages of small print. If space permitted, I could make lengthy quotations of these opinions. But let it suffice to translate here a few choice quotations on pertinent aspects of the question under discussion. For the rest, I will tabulate and summarize these opinions.
1) On the question of a sufficiency for all.
Martinius and Dekker would be in substantial agreement, I fear.
2) On the question for whom Christ died.
The Gelderland delegates state flatly, “… never is Christ said to have died for every man; and this we cannot countenance, seeing that we judge it to be false and to conflict with the divine righteousness, and to be not only useless and of no service for the edifying and comforting of burdened Christians, but also dangerous.' This is followed by an elaborate and careful explanation that terms like 'all' and 'world' do not mean every individual in Scripture.
North Holland and Friesland also pay close attention to these terms, and argue that they refer only to the elect. Besides, several of the opinions connect the death of Christ with the love of God and of Christ and limit that love of God and of Christ to the elect only.
3) On the co-extensiveness of merit and application.
Almost without exception (Bremen and the British are notable exceptions) the opinions insist that the merit of Christ's death and the application of those merits stand in unbreakable connection and are limited to the elect only.
With the above the entire spirit of Dordt agrees. There were only two who might sustain Dekker. They were Martinius of Bremen and, to an extent, the British theologians, one of whom, Dr. Thomas Goad, later became an avowed Arminian.
Is then Professor Dekker at all supported by Dordrecht? On the contrary, he is condemned. Dordt would have placed him in the category of the Arminians, sad to say.
Remember that Professor Dekker has an atonement that is universal in sufficiency, in availability, and in the desire of God. In these three respects he wants to say that Christ died for all men, and can say, he claims, to every man, 'Christ died for you.” In only one respect will he limit the atonement, i.e., in its efficacy.
But notice that by his own definition Dekker's atonement may be divided into a two-fold classification, namely, an ineffectual atonement and an ineffectual atonement. His first three aspects (of universal atonement), as over against the fourth (limited, effectual atonement) would have to be classed as ineffectual. Now what is an ineffectual atonement? It is an atonement that does not really atone, a redemptive love that does not redeem, a satisfaction that does not satisfy, a substitution that does not substitute, a divine desire that does not reach its end.
And all these are contrary to Dordt, contrary to Dordt’s understanding of the Scriptures, and, according to Dordt, unworthy of a sovereign God.
May this doctrine of absolutely limited atonement, and of truly effectual atonement, permeate the life and witness of the Church in full power!
Homer C. Hoeksema was born in Grand Rapids, MI on January 30, 1923. He was the second son of Herman Hoeksema and born during the turmoil of the Common Grace controversy which led to the formation of the Protestant Reformed Churches.
He graduated from Calvin College and then the Protestant Reformed Seminary. He served the Protestant Reformed congregation at Doon, Iowa from 1949 to 1955 and later the Protestant Reformed congregation at South Holland, Illinois from 1955 to 1959.
In 1959 he was called to serve as professor in the Protestant Reformed Seminary, a position he held until his emeritation in 1989. He taught the departments of Dogmatics and New Testament studies. He served for many years as the editor of The Standard Bearer and wrote various significant books--the main one, a study of the Canons of Dordt titled: The Voice of the Fathers.
He was taken to glory on July 17, 1989.
Latest from Hoeksema, Homer C.


Greater Sudbury Time zone: EDT - Eastern Daylight Time.
When DST ends, the time zone in Greater Sudbury will return to EST (Eastern Standard Time).
Afghanistan - Kabul Kabul is 8 hours, 30 minutes ahead of Greater Sudbury.
Albania - Tirane Tirane is 6 hours ahead of Greater Sudbury.
Algeria - Algiers Algiers is 5 hours ahead of Greater Sudbury.
American Samoa - Pago Pago Pago Pago is 7 hours behind Greater Sudbury.
Andorra - Andorra La Vella Andorra La Vella is 6 hours ahead of Greater Sudbury.
Angola - Luanda Luanda is 5 hours ahead of Greater Sudbury.
Anguilla - The Valley There is no time difference between The Valley and Greater Sudbury.
Antigua and Barbuda - Saint Johns There is no time difference between Saint Johns and Greater Sudbury.
Argentina - Buenos Aires Buenos Aires is 1 hour ahead of Greater Sudbury.
Argentina - Buenos Aires - La Plata La Plata is 1 hour ahead of Greater Sudbury.
Argentina - Buenos Aires - Mar del Plata Mar del Plata is 1 hour ahead of Greater Sudbury.
Argentina - Mendoza - Mendoza Mendoza is 1 hour ahead of Greater Sudbury.
Argentina - Salta - Salta Salta is 1 hour ahead of Greater Sudbury.
Argentina - Santa Fe - Rosario Rosario is 1 hour ahead of Greater Sudbury.
Argentina - Tucuman - Tucuman Tucuman is 1 hour ahead of Greater Sudbury.
Armenia - Yerevan Yerevan is 8 hours ahead of Greater Sudbury.
Aruba - Oranjestad There is no time difference between Oranjestad and Greater Sudbury.
Australia - ACT - Canberra Canberra is 14 hours ahead of Greater Sudbury.
Australia - Christmas Island - The Settlement The Settlement is 11 hours ahead of Greater Sudbury.
Australia - Lord Howe Island - Lord Howe Island Lord Howe Island is 14 hours, 30 minutes ahead of Greater Sudbury.
Australia - New South Wales - Sydney Sydney is 14 hours ahead of Greater Sudbury.
Australia - Northern Territory - Darwin Darwin is 13 hours, 30 minutes ahead of Greater Sudbury.
Australia - Queensland - Brisbane Brisbane is 14 hours ahead of Greater Sudbury.
Australia - South Australia - Adelaide Adelaide is 13 hours, 30 minutes ahead of Greater Sudbury.
Australia - Tasmania - Hobart Hobart is 14 hours ahead of Greater Sudbury.
Australia - Victoria - Melbourne Melbourne is 14 hours ahead of Greater Sudbury.
Australia - Western Australia - Perth Perth is 12 hours ahead of Greater Sudbury.
Austria - Salzburg Salzburg is 6 hours ahead of Greater Sudbury.
Austria - Vienna Vienna is 6 hours ahead of Greater Sudbury.
Azerbaijan - Baku Baku is 8 hours ahead of Greater Sudbury.
Bahamas - Nassau There is no time difference between Nassau and Greater Sudbury.
Bahrain - Manama Manama is 7 hours ahead of Greater Sudbury.
Bangladesh - Chittagong Chittagong is 10 hours ahead of Greater Sudbury.
Bangladesh - Dhaka Dhaka is 10 hours ahead of Greater Sudbury.
Bangladesh - Khulna Khulna is 10 hours ahead of Greater Sudbury.
Barbados - Bridgetown There is no time difference between Bridgetown and Greater Sudbury.
Belarus - Minsk Minsk is 7 hours ahead of Greater Sudbury.
Belgium - Brussels Brussels is 6 hours ahead of Greater Sudbury.
Belize - Belmopan Belmopan is 2 hours behind Greater Sudbury.
Benin - Porto Novo Porto Novo is 5 hours ahead of Greater Sudbury.
Bermuda - Hamilton (Bermuda) Hamilton (Bermuda) is 1 hour ahead of Greater Sudbury.
Bhutan - Thimphu Thimphu is 10 hours ahead of Greater Sudbury.
Bolivia - La Paz There is no time difference between La Paz and Greater Sudbury.
Bosnia Herzegovina - Sarajevo Sarajevo is 6 hours ahead of Greater Sudbury.
Botswana - Gaborone Gaborone is 6 hours ahead of Greater Sudbury.
Brazil - Acre - Rio Branco Rio Branco is 1 hour behind Greater Sudbury.
Brazil - Amazonas - Manaus There is no time difference between Manaus and Greater Sudbury.
Brazil - Bahia - Salvador Salvador is 1 hour ahead of Greater Sudbury.
Brazil - Distrito Federal - Brasilia Brasilia is 1 hour ahead of Greater Sudbury.
Brazil - Pernambuco - Fernando de Noronha Fernando de Noronha is 2 hours ahead of Greater Sudbury.
Brazil - Pernambuco - Recife Recife is 1 hour ahead of Greater Sudbury.
Brazil - Rio de Janeiro - Rio de Janeiro Rio de Janeiro is 1 hour ahead of Greater Sudbury.
Brazil - Rio Grande do Sul - Porto Alegre Porto Alegre is 1 hour ahead of Greater Sudbury.
Brazil - Sao Paulo - Sao Paulo Sao Paulo is 1 hour ahead of Greater Sudbury.
British Virgin Islands - Tortola - Road Town There is no time difference between Road Town and Greater Sudbury.
Brunei - Bandar Seri Begawan Bandar Seri Begawan is 12 hours ahead of Greater Sudbury.
Bulgaria - Sofia Sofia is 7 hours ahead of Greater Sudbury.
Burkina Faso - Ouagadougou Ouagadougou is 4 hours ahead of Greater Sudbury.
Burundi - Bujumbura Bujumbura is 6 hours ahead of Greater Sudbury.
Cambodia - Phnom Penh Phnom Penh is 11 hours ahead of Greater Sudbury.
Cameroon - Yaounde Yaounde is 5 hours ahead of Greater Sudbury.
Canada - Alberta - Calgary Calgary is 2 hours behind Greater Sudbury.
Canada - Alberta - Edmonton Edmonton is 2 hours behind Greater Sudbury.
Canada - British Columbia - Surrey Surrey is 3 hours behind Greater Sudbury.
Canada - British Columbia - Vancouver Vancouver is 3 hours behind Greater Sudbury.
Canada - British Columbia - Victoria Victoria is 3 hours behind Greater Sudbury.
Canada - Manitoba - Winnipeg Winnipeg is 1 hour behind Greater Sudbury.
Canada - New Brunswick - Saint John Saint John is 1 hour ahead of Greater Sudbury.
Canada - Newfoundland and Labrador - St. Johns St. Johns is 1 hour, 30 minutes ahead of Greater Sudbury.
Canada - Northwest Territories - Yellowknife Yellowknife is 2 hours behind Greater Sudbury.
Canada - Nova Scotia - Halifax Halifax is 1 hour ahead of Greater Sudbury.
Canada - Nunavut Territory - Iqaluit There is no time difference between Iqaluit and Greater Sudbury.
Canada - Ontario - Brampton There is no time difference between Brampton and Greater Sudbury.
Canada - Ontario - Hamilton (Canada) There is no time difference between Hamilton (Canada) and Greater Sudbury.
Canada - Ontario - London (Canada) There is no time difference between London (Canada) and Greater Sudbury.
Canada - Ontario - Markham There is no time difference between Markham and Greater Sudbury.
Canada - Ontario - Mississauga There is no time difference between Mississauga and Greater Sudbury.
Canada - Ontario - Ottawa There is no time difference between Ottawa and Greater Sudbury.
Canada - Ontario - Toronto There is no time difference between Toronto and Greater Sudbury.
Canada - Ontario - Windsor There is no time difference between Windsor and Greater Sudbury.
Canada - Pr.Edward I - Charlottetown Charlottetown is 1 hour ahead of Greater Sudbury.
Canada - Quebec - Gatineau There is no time difference between Gatineau and Greater Sudbury.
Canada - Quebec - Laval There is no time difference between Laval and Greater Sudbury.
Canada - Quebec - Longueuil There is no time difference between Longueuil and Greater Sudbury.
Canada - Quebec - Montreal There is no time difference between Montreal and Greater Sudbury.
Canada - Quebec - Quebec There is no time difference between Quebec and Greater Sudbury.
Canada - Saskatchewan - Regina Regina is 2 hours behind Greater Sudbury.
Canada - Saskatchewan - Saskatoon Saskatoon is 2 hours behind Greater Sudbury.
Canada - Yukon Territory - Whitehorse Whitehorse is 3 hours behind Greater Sudbury.
Cape Verde - Praia Praia is 3 hours ahead of Greater Sudbury.
Cayman Islands - George Town(Cayman Islands) George Town(Cayman Islands) is 1 hour behind Greater Sudbury.
Central African Republic - Bangui Bangui is 5 hours ahead of Greater Sudbury.
Chad - Ndjamena Ndjamena is 5 hours ahead of Greater Sudbury.
Chile - Easter Island Easter Island is 2 hours behind Greater Sudbury.
Chile - Santiago There is no time difference between Santiago and Greater Sudbury.
China - Beijing Municipality - Beijing Beijing is 12 hours ahead of Greater Sudbury.
China - Chongqing Municipality - Chongqing Chongqing is 12 hours ahead of Greater Sudbury.
China - Fujian - Foochow Foochow is 12 hours ahead of Greater Sudbury.
China - Gansu - Lanchow Lanchow is 12 hours ahead of Greater Sudbury.
China - Guangdong - Shenzhen Shenzhen is 12 hours ahead of Greater Sudbury.
China - Guizhou - Guiyang Guiyang is 12 hours ahead of Greater Sudbury.
China - Hebei - Shijiazhuang Shijiazhuang is 12 hours ahead of Greater Sudbury.
China - Hebei - Tangshan Tangshan is 12 hours ahead of Greater Sudbury.
China - Heilongjiang - Harbin Harbin is 12 hours ahead of Greater Sudbury.
China - Heilongjiang - Qiqihar Qiqihar is 12 hours ahead of Greater Sudbury.
China - Henan - Luoyang Luoyang is 12 hours ahead of Greater Sudbury.
China - Henan - Zhengzhou Zhengzhou is 12 hours ahead of Greater Sudbury.
China - Hubei - Wuhan Wuhan is 12 hours ahead of Greater Sudbury.
China - Hunan - Changsha Changsha is 12 hours ahead of Greater Sudbury.
China - Inner Mongolia - Baotou Baotou is 12 hours ahead of Greater Sudbury.
China - Jiangxi - Nanchang Nanchang is 12 hours ahead of Greater Sudbury.
China - Jilin - Changchun Changchun is 12 hours ahead of Greater Sudbury.
China - Jilin - Jilin Jilin is 12 hours ahead of Greater Sudbury.
China - Liaoning - Anshan Anshan is 12 hours ahead of Greater Sudbury.
China - Liaoning - Dalian Dalian is 12 hours ahead of Greater Sudbury.
China - Liaoning - Fushun Fushun is 12 hours ahead of Greater Sudbury.
China - Liaoning - Jinzhou Jinzhou is 12 hours ahead of Greater Sudbury.
China - Macau - Macau Macau is 12 hours ahead of Greater Sudbury.
China - Shaanxi - Sian Sian is 12 hours ahead of Greater Sudbury.
China - Shandong - Jinan Jinan is 12 hours ahead of Greater Sudbury.
China - Shandong - Tsingtao Tsingtao is 12 hours ahead of Greater Sudbury.
China - Shandong - Zibo Zibo is 12 hours ahead of Greater Sudbury.
China - Shanghai Municipality - Shanghai Shanghai is 12 hours ahead of Greater Sudbury.
China - Shanxi - Taiyuan Taiyuan is 12 hours ahead of Greater Sudbury.
China - Sichuan - Chengdu Chengdu is 12 hours ahead of Greater Sudbury.
China - Tianjin Municipality - Tianjin Tianjin is 12 hours ahead of Greater Sudbury.
China - Tibet - Lhasa Lhasa is 12 hours ahead of Greater Sudbury.
China - Yunnan - Kunming Kunming is 12 hours ahead of Greater Sudbury.
China - Zhejiang - Hangzhou Hangzhou is 12 hours ahead of Greater Sudbury.
Colombia - Bogota Bogota is 1 hour behind Greater Sudbury.
Colombia - Cali Cali is 1 hour behind Greater Sudbury.
Colombia - Medellin Medellin is 1 hour behind Greater Sudbury.
Comoros - Moroni Moroni is 7 hours ahead of Greater Sudbury.
Congo - Brazzaville Brazzaville is 5 hours ahead of Greater Sudbury.
Congo Dem. Rep. - Kinshasa Kinshasa is 5 hours ahead of Greater Sudbury.
Congo Dem. Rep. - Lubumbashi Lubumbashi is 6 hours ahead of Greater Sudbury.
Cook Islands - Rarotonga Rarotonga is 6 hours behind Greater Sudbury.
Costa Rica - San Jose (Costa Rica) San Jose (Costa Rica) is 2 hours behind Greater Sudbury.
Cote dIvoire - Abidjan Abidjan is 4 hours ahead of Greater Sudbury.
Cote dIvoire - Yamoussoukro Yamoussoukro is 4 hours ahead of Greater Sudbury.
Croatia - Zagreb Zagreb is 6 hours ahead of Greater Sudbury.
Cuba - Havana There is no time difference between Havana and Greater Sudbury.
Curacao - Willemstad There is no time difference between Willemstad and Greater Sudbury.
Cyprus - Nicosia Nicosia is 7 hours ahead of Greater Sudbury.
Czech Republic - Prague Prague is 6 hours ahead of Greater Sudbury.
Denmark - Copenhagen Copenhagen is 6 hours ahead of Greater Sudbury.
Djibouti - Djibouti Djibouti is 7 hours ahead of Greater Sudbury.
Dominica - Roseau There is no time difference between Roseau and Greater Sudbury.
Dominican Republic - Santo Domingo There is no time difference between Santo Domingo and Greater Sudbury.
Ecuador - Galapagos Islands Galapagos Islands is 2 hours behind Greater Sudbury.
Ecuador - Guayaquil Guayaquil is 1 hour behind Greater Sudbury.
Ecuador - Quito Quito is 1 hour behind Greater Sudbury.
Egypt - Al Jizah Al Jizah is 6 hours ahead of Greater Sudbury.
Egypt - Alexandria Alexandria is 6 hours ahead of Greater Sudbury.
Egypt - Cairo Cairo is 6 hours ahead of Greater Sudbury.
El Salvador - San Salvador San Salvador is 2 hours behind Greater Sudbury.
El Salvador - Santa Ana Santa Ana is 2 hours behind Greater Sudbury.
Equatorial Guinea - Malabo Malabo is 5 hours ahead of Greater Sudbury.
Eritrea - Asmara Asmara is 7 hours ahead of Greater Sudbury.
Estonia - Tallinn Tallinn is 7 hours ahead of Greater Sudbury.
Ethiopia - Addis Ababa Addis Ababa is 7 hours ahead of Greater Sudbury.
Falkland Islands - Stanley Stanley is 1 hour ahead of Greater Sudbury.
Faroe Islands - Faroe Islands - Torshavn Torshavn is 5 hours ahead of Greater Sudbury.
Fiji - Suva Suva is 16 hours ahead of Greater Sudbury.
Finland - Helsinki Helsinki is 7 hours ahead of Greater Sudbury.
France - Nice Nice is 6 hours ahead of Greater Sudbury.
France - Paris Paris is 6 hours ahead of Greater Sudbury.
France - Corsica - Bastia Bastia is 6 hours ahead of Greater Sudbury.
French Guiana - Cayenne Cayenne is 1 hour ahead of Greater Sudbury.
French Polynesia - Gambier Islands Gambier Islands is 5 hours behind Greater Sudbury.
French Polynesia - Marquesas Islands - Taiohae Taiohae is 5 hours, 30 minutes behind Greater Sudbury.
French Polynesia - Tahiti - Papeete Papeete is 6 hours behind Greater Sudbury.
French Southern Territories - Port-aux-Francais Port-aux-Francais is 9 hours ahead of Greater Sudbury.
Gabon - Libreville Libreville is 5 hours ahead of Greater Sudbury.
Gambia - Banjul Banjul is 4 hours ahead of Greater Sudbury.
Gaza Strip - Gaza Gaza is 7 hours ahead of Greater Sudbury.
Georgia - Tbilisi Tbilisi is 8 hours ahead of Greater Sudbury.
Germany - Baden-Wurttemberg - Stuttgart Stuttgart is 6 hours ahead of Greater Sudbury.
Germany - Bavaria - Munich Munich is 6 hours ahead of Greater Sudbury.
Germany - Berlin - Berlin Berlin is 6 hours ahead of Greater Sudbury.
Germany - Hamburg - Hamburg Hamburg is 6 hours ahead of Greater Sudbury.
Germany - Hesse - Frankfurt Frankfurt is 6 hours ahead of Greater Sudbury.
Germany - North Rhine-Westphalia - Dusseldorf Dusseldorf is 6 hours ahead of Greater Sudbury.
Ghana - Accra Accra is 4 hours ahead of Greater Sudbury.
Gibraltar - Gibraltar Gibraltar is 6 hours ahead of Greater Sudbury.
Greece - Athens Athens is 7 hours ahead of Greater Sudbury.
Greenland - Nuuk Nuuk is 2 hours ahead of Greater Sudbury.
Grenada - Saint Georges There is no time difference between Saint Georges and Greater Sudbury.
Guadeloupe - Basse-Terre There is no time difference between Basse-Terre and Greater Sudbury.
Guatemala - Guatemala Guatemala is 2 hours behind Greater Sudbury.
Guinea - Conakry Conakry is 4 hours ahead of Greater Sudbury.
Guinea Bissau - Bissau Bissau is 4 hours ahead of Greater Sudbury.
Guyana - Georgetown There is no time difference between Georgetown and Greater Sudbury.
Haiti - Port-au-Prince There is no time difference between Port-au-Prince and Greater Sudbury.
Honduras - Tegucigalpa Tegucigalpa is 2 hours behind Greater Sudbury.
Hong Kong - Hong Kong Hong Kong is 12 hours ahead of Greater Sudbury.
Hong Kong - Kowloon Kowloon is 12 hours ahead of Greater Sudbury.
Hungary - Budapest Budapest is 6 hours ahead of Greater Sudbury.
Iceland - Reykjavik Reykjavik is 4 hours ahead of Greater Sudbury.
India - Andhra Pradesh - Visakhapatnam Visakhapatnam is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Bihar - Patna Patna is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Chandigarh - Chandigarh Chandigarh is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Delhi - New Delhi New Delhi is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Gujarat - Ahmedabad Ahmedabad is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Gujarat - Surat Surat is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Gujarat - Vadodara Vadodara is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Karnataka - Bangalore Bangalore is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Madhya Pradesh - Indore Indore is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Maharashtra - Mumbai Mumbai is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Maharashtra - Nagpur Nagpur is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Maharashtra - Pune Pune is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Orissa - Bhubaneshwar Bhubaneshwar is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Punjab - Ludhiana Ludhiana is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Rajasthan - Jaipur Jaipur is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Tamil Nadu - Chennai Chennai is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Telangana - Hyderabad Hyderabad is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Uttar Pradesh - Agra Agra is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Uttar Pradesh - Kanpur Kanpur is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Uttar Pradesh - Lucknow Lucknow is 9 hours, 30 minutes ahead of Greater Sudbury.
India - Uttar Pradesh - Varanasi Varanasi is 9 hours, 30 minutes ahead of Greater Sudbury.
India - West Bengal - Kolkata Kolkata is 9 hours, 30 minutes ahead of Greater Sudbury.
Indonesia - Bali - Denpasar Denpasar is 12 hours ahead of Greater Sudbury.
Indonesia - Bali - Singaraja Singaraja is 12 hours ahead of Greater Sudbury.
Indonesia - Java - Bandung Bandung is 11 hours ahead of Greater Sudbury.
Indonesia - Java - Jakarta Jakarta is 11 hours ahead of Greater Sudbury.
Indonesia - Java - Malang Malang is 11 hours ahead of Greater Sudbury.
Indonesia - Java - Semarang Semarang is 11 hours ahead of Greater Sudbury.
Indonesia - Java - Surabaya Surabaya is 11 hours ahead of Greater Sudbury.
Indonesia - Java - Surakarta Surakarta is 11 hours ahead of Greater Sudbury.
Indonesia - Kalimantan - Balikpapan Balikpapan is 12 hours ahead of Greater Sudbury.
Indonesia - Lombok - Mataram Mataram is 12 hours ahead of Greater Sudbury.
Indonesia - Papua - Jayapura Jayapura is 13 hours ahead of Greater Sudbury.
Indonesia - Sumatra - Medan Medan is 11 hours ahead of Greater Sudbury.
Indonesia - Sumatra - Palembang Palembang is 11 hours ahead of Greater Sudbury.
Indonesia - East Nusa Tenggara - Kupang Kupang is 12 hours ahead of Greater Sudbury.
Iran - Esfahan Esfahan is 8 hours, 30 minutes ahead of Greater Sudbury.
Iran - Tehran Tehran is 8 hours, 30 minutes ahead of Greater Sudbury.
Iran - Yazd Yazd is 8 hours, 30 minutes ahead of Greater Sudbury.
Iraq - Baghdad Baghdad is 7 hours ahead of Greater Sudbury.
Iraq - Basra Basra is 7 hours ahead of Greater Sudbury.
Ireland - Dublin Dublin is 5 hours ahead of Greater Sudbury.
Israel - Jerusalem Jerusalem is 7 hours ahead of Greater Sudbury.
Israel - Tel Aviv Tel Aviv is 7 hours ahead of Greater Sudbury.
Italy - Milan Milan is 6 hours ahead of Greater Sudbury.
Italy - Naples Naples is 6 hours ahead of Greater Sudbury.
Italy - Rome Rome is 6 hours ahead of Greater Sudbury.
Italy - Turin Turin is 6 hours ahead of Greater Sudbury.
Italy - Venice Venice is 6 hours ahead of Greater Sudbury.
Jamaica - Kingston (Jamaica) Kingston (Jamaica) is 1 hour behind Greater Sudbury.
Japan - Fukuoka Fukuoka is 13 hours ahead of Greater Sudbury.
Japan - Hiroshima Hiroshima is 13 hours ahead of Greater Sudbury.
Japan - Kawasaki Kawasaki is 13 hours ahead of Greater Sudbury.
Japan - Kitakyushu Kitakyushu is 13 hours ahead of Greater Sudbury.
Japan - Kobe Kobe is 13 hours ahead of Greater Sudbury.
Japan - Kyoto Kyoto is 13 hours ahead of Greater Sudbury.
Japan - Nagoya Nagoya is 13 hours ahead of Greater Sudbury.
Japan - Okayama Okayama is 13 hours ahead of Greater Sudbury.
Japan - Osaka Osaka is 13 hours ahead of Greater Sudbury.
Japan - Sapporo Sapporo is 13 hours ahead of Greater Sudbury.
Japan - Sendai Sendai is 13 hours ahead of Greater Sudbury.
Japan - Tokyo Tokyo is 13 hours ahead of Greater Sudbury.
Japan - Yokohama Yokohama is 13 hours ahead of Greater Sudbury.
Jordan - Amman Amman is 7 hours ahead of Greater Sudbury.
Kazakhstan - Almaty Almaty is 10 hours ahead of Greater Sudbury.
Kazakhstan - Aqtau Aqtau is 9 hours ahead of Greater Sudbury.
Kazakhstan - Aqtobe Aqtobe is 9 hours ahead of Greater Sudbury.
Kazakhstan - Astana Astana is 10 hours ahead of Greater Sudbury.
Kenya - Nairobi Nairobi is 7 hours ahead of Greater Sudbury.
Kiribati - Tarawa Tarawa is 16 hours ahead of Greater Sudbury.
Kiribati - Christmas Islands - Kiritimati Kiritimati is 18 hours ahead of Greater Sudbury.
Kiribati - Phoenix Islands - Rawaki Rawaki is 17 hours ahead of Greater Sudbury.
Kosovo - Pristina Pristina is 6 hours ahead of Greater Sudbury.
Kuwait - Kuwait City Kuwait City is 7 hours ahead of Greater Sudbury.
Kyrgyzstan - Bishkek Bishkek is 10 hours ahead of Greater Sudbury.
Laos - Vientiane Vientiane is 11 hours ahead of Greater Sudbury.
Latvia - Riga Riga is 7 hours ahead of Greater Sudbury.
Lebanon - Beirut Beirut is 7 hours ahead of Greater Sudbury.
Lesotho - Maseru Maseru is 6 hours ahead of Greater Sudbury.
Liberia - Monrovia Monrovia is 4 hours ahead of Greater Sudbury.
Libya - Tripoli Tripoli is 6 hours ahead of Greater Sudbury.
Liechtenstein - Vaduz Vaduz is 6 hours ahead of Greater Sudbury.
Lithuania - Kaunas Kaunas is 7 hours ahead of Greater Sudbury.
Lithuania - Vilnius Vilnius is 7 hours ahead of Greater Sudbury.
Luxembourg - Luxembourg Luxembourg is 6 hours ahead of Greater Sudbury.
Macedonia - Skopje Skopje is 6 hours ahead of Greater Sudbury.
Madagascar - Antananarivo Antananarivo is 7 hours ahead of Greater Sudbury.
Malawi - Lilongwe Lilongwe is 6 hours ahead of Greater Sudbury.
Malaysia - Kuala Lumpur Kuala Lumpur is 12 hours ahead of Greater Sudbury.
Maldives - Male Male is 9 hours ahead of Greater Sudbury.
Mali - Bamako Bamako is 4 hours ahead of Greater Sudbury.
Malta - Valletta Valletta is 6 hours ahead of Greater Sudbury.
Marshall Islands - Majuro Majuro is 16 hours ahead of Greater Sudbury.
Martinique - Fort-de-France There is no time difference between Fort-de-France and Greater Sudbury.
Mauritania - Nouakchott Nouakchott is 4 hours ahead of Greater Sudbury.
Mauritius - Port Louis Port Louis is 8 hours ahead of Greater Sudbury.
Mayotte - Mamoutzou Mamoutzou is 7 hours ahead of Greater Sudbury.
Mexico - Aguascalientes - Aguascalientes Aguascalientes is 1 hour behind Greater Sudbury.
Mexico - Baja California - Mexicali Mexicali is 3 hours behind Greater Sudbury.
Mexico - Baja California - Tijuana Tijuana is 3 hours behind Greater Sudbury.
Mexico - Chihuahua - Chihuahua Chihuahua is 2 hours behind Greater Sudbury.
Mexico - Federal District - Mexico City Mexico City is 1 hour behind Greater Sudbury.
Mexico - Guanajuato - Leon Leon is 1 hour behind Greater Sudbury.
Mexico - Guerrero - Acapulco Acapulco is 1 hour behind Greater Sudbury.
Mexico - Jalisco - Guadalajara Guadalajara is 1 hour behind Greater Sudbury.
Mexico - Nuevo Leon - Monterrey Monterrey is 1 hour behind Greater Sudbury.
Mexico - Quintana Roo - Cancun Cancun is 1 hour behind Greater Sudbury.
Mexico - San Luis Potosi - San Luis Potosi San Luis Potosi is 1 hour behind Greater Sudbury.
Mexico - Sinaloa - Mazatlan Mazatlan is 2 hours behind Greater Sudbury.
Mexico - Veracruz - Veracruz Veracruz is 1 hour behind Greater Sudbury.
Mexico - Yucatan - Merida Merida is 1 hour behind Greater Sudbury.
Micronesia - Pohnpei - Palikir Palikir is 15 hours ahead of Greater Sudbury.
Moldova - Kishinev Kishinev is 7 hours ahead of Greater Sudbury.
Monaco - Monaco Monaco is 6 hours ahead of Greater Sudbury.
Mongolia - Choibalsan Choibalsan is 12 hours ahead of Greater Sudbury.
Mongolia - Hovd Hovd is 11 hours ahead of Greater Sudbury.
Mongolia - Ulaanbaatar Ulaanbaatar is 12 hours ahead of Greater Sudbury.
Montenegro - Podgorica Podgorica is 6 hours ahead of Greater Sudbury.
Montserrat - Brades There is no time difference between Brades and Greater Sudbury.
Morocco - Casablanca Casablanca is 5 hours ahead of Greater Sudbury.
Morocco - Rabat Rabat is 5 hours ahead of Greater Sudbury.
Morocco - Tangier Tangier is 5 hours ahead of Greater Sudbury.
Mozambique - Maputo Maputo is 6 hours ahead of Greater Sudbury.
Myanmar - Yangon Yangon is 10 hours, 30 minutes ahead of Greater Sudbury.
Namibia - Windhoek Windhoek is 6 hours ahead of Greater Sudbury.
Nauru - Yaren Yaren is 16 hours ahead of Greater Sudbury.
Nepal - Kathmandu Kathmandu is 9 hours, 45 minutes ahead of Greater Sudbury.
Netherlands - Amsterdam Amsterdam is 6 hours ahead of Greater Sudbury.
Netherlands - Rotterdam Rotterdam is 6 hours ahead of Greater Sudbury.
New Caledonia - New Caledonia - Noumea Noumea is 15 hours ahead of Greater Sudbury.
New Zealand - Auckland Auckland is 16 hours ahead of Greater Sudbury.
New Zealand - Chatham Island Chatham Island is 16 hours, 45 minutes ahead of Greater Sudbury.
New Zealand - Christchurch Christchurch is 16 hours ahead of Greater Sudbury.
New Zealand - Wellington Wellington is 16 hours ahead of Greater Sudbury.
Nicaragua - Managua Managua is 2 hours behind Greater Sudbury.
Niger - Niamey Niamey is 5 hours ahead of Greater Sudbury.
Nigeria - Abuja Abuja is 5 hours ahead of Greater Sudbury.
Nigeria - Kano Nigeria Kano Nigeria is 5 hours ahead of Greater Sudbury.
Nigeria - Lagos Lagos is 5 hours ahead of Greater Sudbury.
Niue - Alofi Alofi is 7 hours behind Greater Sudbury.
Norfolk Island - Kingston Kingston is 15 hours, 30 minutes ahead of Greater Sudbury.
North Korea - Pyongyang Pyongyang is 13 hours ahead of Greater Sudbury.
Norway - Oslo Oslo is 6 hours ahead of Greater Sudbury.
Oman - Muscat Muscat is 8 hours ahead of Greater Sudbury.
Pakistan - Faisalabad Faisalabad is 9 hours ahead of Greater Sudbury.
Pakistan - Islamabad Islamabad is 9 hours ahead of Greater Sudbury.
Pakistan - Karachi Karachi is 9 hours ahead of Greater Sudbury.
Pakistan - Lahore Lahore is 9 hours ahead of Greater Sudbury.
Pakistan - Peshawar Peshawar is 9 hours ahead of Greater Sudbury.
Pakistan - Sialkot Sialkot is 9 hours ahead of Greater Sudbury.
Palau - Koror Koror is 13 hours ahead of Greater Sudbury.
Panama - Panama Panama is 1 hour behind Greater Sudbury.
Papua New Guinea - Port Moresby Port Moresby is 14 hours ahead of Greater Sudbury.
Paraguay - Asuncion There is no time difference between Asuncion and Greater Sudbury.
Peru - Lima - Lima Lima is 1 hour behind Greater Sudbury.
Philippines - Cebu City Cebu City is 12 hours ahead of Greater Sudbury.
Philippines - Manila Manila is 12 hours ahead of Greater Sudbury.
Pitcairn Islands - Adamstown Adamstown is 4 hours behind Greater Sudbury.
Poland - Gdansk Gdansk is 6 hours ahead of Greater Sudbury.
Poland - Krakow Krakow is 6 hours ahead of Greater Sudbury.
Poland - Lodz Lodz is 6 hours ahead of Greater Sudbury.
Poland - Poznan Poznan is 6 hours ahead of Greater Sudbury.
Poland - Szczecin Szczecin is 6 hours ahead of Greater Sudbury.
Poland - Warsaw Warsaw is 6 hours ahead of Greater Sudbury.
Poland - Wroclaw Wroclaw is 6 hours ahead of Greater Sudbury.
Portugal - Azores Azores is 4 hours ahead of Greater Sudbury.
Portugal - Lisbon Lisbon is 5 hours ahead of Greater Sudbury.
Portugal - Porto Porto is 5 hours ahead of Greater Sudbury.
Portugal - Madeira - Funchal Funchal is 5 hours ahead of Greater Sudbury.
Puerto Rico - San Juan There is no time difference between San Juan and Greater Sudbury.
Qatar - Doha Doha is 7 hours ahead of Greater Sudbury.
Reunion (French) - Saint-Denis Saint-Denis is 8 hours ahead of Greater Sudbury.
Romania - Bucharest Bucharest is 7 hours ahead of Greater Sudbury.
Russia - Anadyr Anadyr is 16 hours ahead of Greater Sudbury.
Russia - Chelyabinsk Chelyabinsk is 9 hours ahead of Greater Sudbury.
Russia - Kaliningrad Kaliningrad is 6 hours ahead of Greater Sudbury.
Russia - Kazan Kazan is 7 hours ahead of Greater Sudbury.
Russia - Krasnoyarsk Krasnoyarsk is 11 hours ahead of Greater Sudbury.
Russia - Moscow Moscow is 7 hours ahead of Greater Sudbury.
Russia - Murmansk Murmansk is 7 hours ahead of Greater Sudbury.
Russia - Novgorod Novgorod is 7 hours ahead of Greater Sudbury.
Russia - Novosibirsk Novosibirsk is 11 hours ahead of Greater Sudbury.
Russia - Omsk Omsk is 10 hours ahead of Greater Sudbury.
Russia - Perm Perm is 9 hours ahead of Greater Sudbury.
Russia - Petropavlovsk-Kamchatsky Petropavlovsk-Kamchatsky is 16 hours ahead of Greater Sudbury.
Russia - Saint-Petersburg Saint-Petersburg is 7 hours ahead of Greater Sudbury.
Russia - Samara Samara is 8 hours ahead of Greater Sudbury.
Russia - Sochi Sochi is 7 hours ahead of Greater Sudbury.
Russia - Ufa Ufa is 9 hours ahead of Greater Sudbury.
Russia - Vladivostok Vladivostok is 14 hours ahead of Greater Sudbury.
Russia - Yekaterinburg Yekaterinburg is 9 hours ahead of Greater Sudbury.
Russia - Yuzhno-Sakhalinsk Yuzhno-Sakhalinsk is 15 hours ahead of Greater Sudbury.
Rwanda - Kigali Kigali is 6 hours ahead of Greater Sudbury.
Saint Kitts and Nevis - Basseterre There is no time difference between Basseterre and Greater Sudbury.
Saint Lucia - Castries There is no time difference between Castries and Greater Sudbury.
Saint Vincent Grenadines - Kingstown There is no time difference between Kingstown and Greater Sudbury.
Samoa - Apia Apia is 17 hours ahead of Greater Sudbury.
San Marino - San Marino San Marino is 6 hours ahead of Greater Sudbury.
Sao Tome and Principe - Sao Tome Sao Tome is 4 hours ahead of Greater Sudbury.
Saudi Arabia - Jeddah Jeddah is 7 hours ahead of Greater Sudbury.
Saudi Arabia - Mecca Mecca is 7 hours ahead of Greater Sudbury.
Saudi Arabia - Riyadh Riyadh is 7 hours ahead of Greater Sudbury.
Senegal - Dakar Dakar is 4 hours ahead of Greater Sudbury.
Serbia - Belgrade Belgrade is 6 hours ahead of Greater Sudbury.
Seychelles - Victoria (Seychelles) Victoria (Seychelles) is 8 hours ahead of Greater Sudbury.
Sierra Leone - Freetown Freetown is 4 hours ahead of Greater Sudbury.
Singapore - Singapore Singapore is 12 hours ahead of Greater Sudbury.
Slovakia - Bratislava Bratislava is 6 hours ahead of Greater Sudbury.
Slovenia - Ljubljana Ljubljana is 6 hours ahead of Greater Sudbury.
Solomon Islands - Honiara Honiara is 15 hours ahead of Greater Sudbury.
Somalia - Mogadishu Mogadishu is 7 hours ahead of Greater Sudbury.
South Africa - Cape Town Cape Town is 6 hours ahead of Greater Sudbury.
South Africa - Durban Durban is 6 hours ahead of Greater Sudbury.
South Africa - Johannesburg Johannesburg is 6 hours ahead of Greater Sudbury.
South Africa - Port Elizabeth Port Elizabeth is 6 hours ahead of Greater Sudbury.
South Africa - Pretoria Pretoria is 6 hours ahead of Greater Sudbury.
South Korea - Busan Busan is 13 hours ahead of Greater Sudbury.
South Korea - Incheon Incheon is 13 hours ahead of Greater Sudbury.
South Korea - Seoul Seoul is 13 hours ahead of Greater Sudbury.
South Korea - Taegu Taegu is 13 hours ahead of Greater Sudbury.
South Sudan - Juba Juba is 7 hours ahead of Greater Sudbury.
Spain - Cordoba Cordoba is 6 hours ahead of Greater Sudbury.
Spain - La Coruna La Coruna is 6 hours ahead of Greater Sudbury.
Spain - Madrid Madrid is 6 hours ahead of Greater Sudbury.
Spain - Barcelona - Barcelona Barcelona is 6 hours ahead of Greater Sudbury.
Spain - Canary Islands - Las Palmas Las Palmas is 5 hours ahead of Greater Sudbury.
Spain - Majorca - Palma Palma is 6 hours ahead of Greater Sudbury.
Sri Lanka - Colombo Colombo is 9 hours, 30 minutes ahead of Greater Sudbury.
Sudan - Khartoum Khartoum is 6 hours ahead of Greater Sudbury.
Suriname - Paramaribo Paramaribo is 1 hour ahead of Greater Sudbury.
eSwatini - Mbabane Mbabane is 6 hours ahead of Greater Sudbury.
Sweden - Stockholm Stockholm is 6 hours ahead of Greater Sudbury.
Switzerland - Basel Basel is 6 hours ahead of Greater Sudbury.
Switzerland - Bern Bern is 6 hours ahead of Greater Sudbury.
Switzerland - Geneva Geneva is 6 hours ahead of Greater Sudbury.
Switzerland - Lausanne Lausanne is 6 hours ahead of Greater Sudbury.
Switzerland - Zurich Zurich is 6 hours ahead of Greater Sudbury.
Syria - Damascus Damascus is 7 hours ahead of Greater Sudbury.
Taiwan - Kaohsiung Kaohsiung is 12 hours ahead of Greater Sudbury.
Taiwan - Taipei Taipei is 12 hours ahead of Greater Sudbury.
Tajikistan - Dushanbe Dushanbe is 9 hours ahead of Greater Sudbury.
Tanzania - Dar es Salaam Dar es Salaam is 7 hours ahead of Greater Sudbury.
Tanzania - Dodoma Dodoma is 7 hours ahead of Greater Sudbury.
Thailand - Bangkok Bangkok is 11 hours ahead of Greater Sudbury.
Thailand - Khon Kaen Khon Kaen is 11 hours ahead of Greater Sudbury.
Timor Leste - Dili Dili is 13 hours ahead of Greater Sudbury.
Togo - Lome Lome is 4 hours ahead of Greater Sudbury.
Tokelau - Tokelau - Fakaofo Fakaofo is 18 hours ahead of Greater Sudbury.
Tonga - Nukualofa Nukualofa is 17 hours ahead of Greater Sudbury.
Trinidad and Tobago - Port of Spain There is no time difference between Port of Spain and Greater Sudbury.
Tunisia - Tunis Tunis is 5 hours ahead of Greater Sudbury.
Turkey - Ankara Ankara is 7 hours ahead of Greater Sudbury.
Turkey - Istanbul Istanbul is 7 hours ahead of Greater Sudbury.
Turkey - Izmir Izmir is 7 hours ahead of Greater Sudbury.
Turkmenistan - Ashgabat Ashgabat is 9 hours ahead of Greater Sudbury.
Tuvalu - Funafuti Funafuti is 16 hours ahead of Greater Sudbury.
UAE - Abu Dhabi - Abu Dhabi Abu Dhabi is 8 hours ahead of Greater Sudbury.
UAE - Dubai - Dubai Dubai is 8 hours ahead of Greater Sudbury.
Uganda - Kampala Kampala is 7 hours ahead of Greater Sudbury.
UK - England - Birmingham (UK) Birmingham (UK) is 5 hours ahead of Greater Sudbury.
UK - England - Liverpool Liverpool is 5 hours ahead of Greater Sudbury.
UK - England - London London is 5 hours ahead of Greater Sudbury.
UK - England - Southampton Southampton is 5 hours ahead of Greater Sudbury.
UK - Northern Ireland - Belfast Belfast is 5 hours ahead of Greater Sudbury.
UK - Scotland - Edinburgh Edinburgh is 5 hours ahead of Greater Sudbury.
UK - Scotland - Glasgow Glasgow is 5 hours ahead of Greater Sudbury.
UK - Wales - Cardiff Cardiff is 5 hours ahead of Greater Sudbury.
Ukraine - Kiev Kiev is 7 hours ahead of Greater Sudbury.
Ukraine - Odesa Odesa is 7 hours ahead of Greater Sudbury.
Uruguay - Montevideo Montevideo is 1 hour ahead of Greater Sudbury.
USA - Alabama - Birmingham (US) Birmingham (US) is 1 hour behind Greater Sudbury.
USA - Alabama - Mobile Mobile is 1 hour behind Greater Sudbury.
USA - Alabama - Montgomery Montgomery is 1 hour behind Greater Sudbury.
USA - Alaska - Adak Adak is 5 hours behind Greater Sudbury.
USA - Alaska - Anchorage Anchorage is 4 hours behind Greater Sudbury.
USA - Alaska - Fairbanks Fairbanks is 4 hours behind Greater Sudbury.
USA - Alaska - Juneau Juneau is 4 hours behind Greater Sudbury.
USA - Alaska - Nome Nome is 4 hours behind Greater Sudbury.
USA - Alaska - Unalaska Unalaska is 4 hours behind Greater Sudbury.
USA - Arizona - Mesa Mesa is 3 hours behind Greater Sudbury.
USA - Arizona - Phoenix Phoenix is 3 hours behind Greater Sudbury.
USA - Arizona - Tucson Tucson is 3 hours behind Greater Sudbury.
USA - Arkansas - Little Rock Little Rock is 1 hour behind Greater Sudbury.
USA - California - Anaheim Anaheim is 3 hours behind Greater Sudbury.
USA - California - Fresno Fresno is 3 hours behind Greater Sudbury.
USA - California - Long Beach Long Beach is 3 hours behind Greater Sudbury.
USA - California - Los Angeles Los Angeles is 3 hours behind Greater Sudbury.
USA - California - Oakland Oakland is 3 hours behind Greater Sudbury.
USA - California - Riverside Riverside is 3 hours behind Greater Sudbury.
USA - California - Sacramento Sacramento is 3 hours behind Greater Sudbury.
USA - California - San Bernardino San Bernardino is 3 hours behind Greater Sudbury.
USA - California - San Diego San Diego is 3 hours behind Greater Sudbury.
USA - California - San Francisco San Francisco is 3 hours behind Greater Sudbury.
USA - California - San Jose San Jose is 3 hours behind Greater Sudbury.
USA - California - Stockton Stockton is 3 hours behind Greater Sudbury.
USA - Colorado - Aurora Aurora is 2 hours behind Greater Sudbury.
USA - Colorado - Denver Denver is 2 hours behind Greater Sudbury.
USA - Connecticut - Hartford There is no time difference between Hartford and Greater Sudbury.
USA - Delaware - Dover There is no time difference between Dover and Greater Sudbury.
USA - District of Columbia - Washington DC There is no time difference between Washington DC and Greater Sudbury.
USA - Florida - Jacksonville There is no time difference between Jacksonville and Greater Sudbury.
USA - Florida - Miami There is no time difference between Miami and Greater Sudbury.
USA - Florida - Orlando There is no time difference between Orlando and Greater Sudbury.
USA - Florida - Pensacola Pensacola is 1 hour behind Greater Sudbury.
USA - Florida - St. Petersburg There is no time difference between St. Petersburg and Greater Sudbury.
USA - Florida - Tampa There is no time difference between Tampa and Greater Sudbury.
USA - Georgia - Atlanta There is no time difference between Atlanta and Greater Sudbury.
USA - Hawaii - Honolulu Honolulu is 6 hours behind Greater Sudbury.
USA - Idaho - Boise Boise is 2 hours behind Greater Sudbury.
USA - Illinois - Chicago Chicago is 1 hour behind Greater Sudbury.
USA - Indiana - Indianapolis There is no time difference between Indianapolis and Greater Sudbury.
USA - Iowa - Des Moines Des Moines is 1 hour behind Greater Sudbury.
USA - Kansas - Topeka Topeka is 1 hour behind Greater Sudbury.
USA - Kansas - Wichita Wichita is 1 hour behind Greater Sudbury.
USA - Kentucky - Frankfort There is no time difference between Frankfort and Greater Sudbury.
USA - Kentucky - Lexington-Fayette There is no time difference between Lexington-Fayette and Greater Sudbury.
USA - Kentucky - Louisville There is no time difference between Louisville and Greater Sudbury.
USA - Louisiana - Baton Rouge Baton Rouge is 1 hour behind Greater Sudbury.
USA - Louisiana - New Orleans New Orleans is 1 hour behind Greater Sudbury.
USA - Maine - Augusta There is no time difference between Augusta and Greater Sudbury.
USA - Mariana Islands - Guam Guam is 14 hours ahead of Greater Sudbury.
USA - Maryland - Baltimore There is no time difference between Baltimore and Greater Sudbury.
USA - Massachusetts - Boston There is no time difference between Boston and Greater Sudbury.
USA - Michigan - Detroit There is no time difference between Detroit and Greater Sudbury.
USA - Minnesota - Minneapolis Minneapolis is 1 hour behind Greater Sudbury.
USA - Minnesota - Saint Paul Saint Paul is 1 hour behind Greater Sudbury.
USA - Mississippi - Jackson Jackson is 1 hour behind Greater Sudbury.
USA - Missouri - Jefferson City Jefferson City is 1 hour behind Greater Sudbury.
USA - Missouri - Kansas City Kansas City is 1 hour behind Greater Sudbury.
USA - Missouri - St. Louis St. Louis is 1 hour behind Greater Sudbury.
USA - Montana - Billings Billings is 2 hours behind Greater Sudbury.
USA - Montana - Helena Helena is 2 hours behind Greater Sudbury.
USA - Nebraska - Lincoln Lincoln is 1 hour behind Greater Sudbury.
USA - Nevada - Carson City Carson City is 3 hours behind Greater Sudbury.
USA - Nevada - Las Vegas Las Vegas is 3 hours behind Greater Sudbury.
USA - New Hampshire - Concord There is no time difference between Concord and Greater Sudbury.
USA - New Jersey - Jersey City There is no time difference between Jersey City and Greater Sudbury.
USA - New Jersey - Newark There is no time difference between Newark and Greater Sudbury.
USA - New Jersey - Trenton There is no time difference between Trenton and Greater Sudbury.
USA - New Mexico - Albuquerque Albuquerque is 2 hours behind Greater Sudbury.
USA - New Mexico - Santa Fe Santa Fe is 2 hours behind Greater Sudbury.
USA - New York - Albany There is no time difference between Albany and Greater Sudbury.
USA - New York - Buffalo There is no time difference between Buffalo and Greater Sudbury.
USA - New York - New York There is no time difference between New York and Greater Sudbury.
USA - New York - Rochester There is no time difference between Rochester and Greater Sudbury.
USA - North Carolina - Charlotte There is no time difference between Charlotte and Greater Sudbury.
USA - North Carolina - Raleigh There is no time difference between Raleigh and Greater Sudbury.
USA - North Dakota - Bismarck Bismarck is 1 hour behind Greater Sudbury.
USA - Northern Mariana Islands - Saipan Saipan is 14 hours ahead of Greater Sudbury.
USA - Ohio - Akron There is no time difference between Akron and Greater Sudbury.
USA - Ohio - Cincinnati There is no time difference between Cincinnati and Greater Sudbury.
USA - Ohio - Cleveland There is no time difference between Cleveland and Greater Sudbury.
USA - Ohio - Columbus There is no time difference between Columbus and Greater Sudbury.
USA - Ohio - Toledo There is no time difference between Toledo and Greater Sudbury.
USA - Oklahoma - Oklahoma City Oklahoma City is 1 hour behind Greater Sudbury.
USA - Oregon - Portland Portland is 3 hours behind Greater Sudbury.
USA - Oregon - Salem Salem is 3 hours behind Greater Sudbury.
USA - Pennsylvania - Harrisburg There is no time difference between Harrisburg and Greater Sudbury.
USA - Pennsylvania - Philadelphia There is no time difference between Philadelphia and Greater Sudbury.
USA - Pennsylvania - Pittsburgh There is no time difference between Pittsburgh and Greater Sudbury.
USA - Rhode Island - Providence There is no time difference between Providence and Greater Sudbury.
USA - South Carolina - Columbia There is no time difference between Columbia and Greater Sudbury.
USA - South Dakota - Pierre Pierre is 1 hour behind Greater Sudbury.
USA - South Dakota - Sioux Falls Sioux Falls is 1 hour behind Greater Sudbury.
USA - Tennessee - Knoxville There is no time difference between Knoxville and Greater Sudbury.
USA - Tennessee - Memphis Memphis is 1 hour behind Greater Sudbury.
USA - Tennessee - Nashville Nashville is 1 hour behind Greater Sudbury.
USA - Texas - Arlington Arlington is 1 hour behind Greater Sudbury.
USA - Texas - Austin Austin is 1 hour behind Greater Sudbury.
USA - Texas - Dallas Dallas is 1 hour behind Greater Sudbury.
USA - Texas - El Paso El Paso is 2 hours behind Greater Sudbury.
USA - Texas - Fort Worth Fort Worth is 1 hour behind Greater Sudbury.
USA - Texas - Houston Houston is 1 hour behind Greater Sudbury.
USA - Texas - San Antonio San Antonio is 1 hour behind Greater Sudbury.
USA - Utah - Salt Lake City Salt Lake City is 2 hours behind Greater Sudbury.
USA - Vermont - Montpelier There is no time difference between Montpelier and Greater Sudbury.
USA - Virginia - Norfolk There is no time difference between Norfolk and Greater Sudbury.
USA - Virginia - Richmond There is no time difference between Richmond and Greater Sudbury.
USA - Virginia - Virginia Beach There is no time difference between Virginia Beach and Greater Sudbury.
USA - Washington - Seattle Seattle is 3 hours behind Greater Sudbury.
USA - West Virginia - Charleston There is no time difference between Charleston and Greater Sudbury.
USA - Wisconsin - Madison Madison is 1 hour behind Greater Sudbury.
USA - Wisconsin - Milwaukee Milwaukee is 1 hour behind Greater Sudbury.
USA - Wyoming - Cheyenne Cheyenne is 2 hours behind Greater Sudbury.
Uzbekistan - Tashkent Tashkent is 9 hours ahead of Greater Sudbury.
Vanuatu - Port Vila Port Vila is 15 hours ahead of Greater Sudbury.
Vatican City State - Vatican City Vatican City is 6 hours ahead of Greater Sudbury.
Venezuela - Caracas There is no time difference between Caracas and Greater Sudbury.
Vietnam - Hanoi Hanoi is 11 hours ahead of Greater Sudbury.
Vietnam - Ho Chi Minh Ho Chi Minh is 11 hours ahead of Greater Sudbury.
West Bank - Bethlehem Bethlehem is 7 hours ahead of Greater Sudbury.
Western Sahara - El Aaiun El Aaiun is 5 hours ahead of Greater Sudbury.
Yemen - Aden Aden is 7 hours ahead of Greater Sudbury.
Yemen - Sana Sana is 7 hours ahead of Greater Sudbury.
Zambia - Lusaka Lusaka is 6 hours ahead of Greater Sudbury.
Zimbabwe - Harare Harare is 6 hours ahead of Greater Sudbury.


This is the second part of “what should the parents of a 4-years old know”. For the first part, please click here.
Being a stay-at-home parent has meant that I am never in a hurry. As the girls do not go to any formal environment, it has meant that they are also never in a hurry. In the case of any issue / any disagreement holding us up, we keep discussing it for whatever time possible, which is all the time. For that matter, even when we are outside the house.
We have consciously avoided getting the girls to act on a conditional basis. I promise that the focus will always be on the task and nothing else, though the task may not fructify at all, number of times.
As none of us is in hurry to do any task / go anywhere, we tend to discuss a lot. The girls keep on asking questions and I keep on giving answers to the best of my and Google’s capabilities. Though, this means that when we actually need to get ready / finish the task in a hurry, we are invariably late.
As a parent, I would want to encourage my child’s curiosity and if that means non-stop chattering and getting late for the task on hand, so be it. At least till the time, we can afford to.
This is another tough one for me. I used to be a person with a short temper. I have realized that whenever I make the environment around not me not so pleasant, it has a direct impact on the girls. Of course, it is not a great discovery. For all the gyaan given to me, I had never heeded. Now, when I have seen the consequences on my daughters, I do not need any other further excuse not to change.
I realize that if there is anything that can bring about a positive change in one’s own self, it is being with a child.
What should the 4-year old be doing? Play, play & play.
It is a tough one. Well, let us be honest. After all the above inputs, what is the expected output? The child may not sing a nursery rhyme when you ask her to. S/he may not be at her best behaviour when you want her to. The child may want just a single pony when you want her to put two.
The resultant action of what we are trying to do with our children means that we have to keep our expectations from them in check.
I suppose around 3-5 years is the age of a child when s/he is actually a child. I have no memories of my being 3-5 years old. The daughters will also not have memories either when they are grown-up. How does it matter that they learn their alphabets/numbers 3-6 months, maybe even more, here and there?
We live only once, the childhood also comes only once. We long for those carefree days. It is not going to return for us though, and we have decided to give it to our daughters to the extent possible.
The last thing I want to know as a parent for my 4-year olds – Be a child.
PS: The things are of course not as good/rosy as I have written above. I am also trying to grow up with my daughters and trying to see how it works out for us, as a family. As mentioned in the beginning, we are a work-in-progress.


Speaking at AIPAC's annual gathering, the vice president on Monday continued the White House campaign of trying to persuade Jewish voters that Democrats aren't with them.
"Anyone who aspires to the highest office in the land should not be afraid to stand with the strongest supporters of Israel in America," Pence said to raucous applause from the crowd at the American Israel Public Affairs Committee's annual policy conference here. "It is wrong to boycott Israel and it is wrong to boycott AIPAC."
Liberal groups asked 2020 Democratic hopefuls to avoid the event, and most have stayed away from it. It’s not clear which, if any, of the Democratic contenders were invited to speak; emails seeking comment on that question from multiple campaigns and spokespeople for the AIPAC conference went unreturned.
"It’s astonishing to think that the party of Harry Truman ... has been co-opted by people who promote rank anti-Semitic rhetoric," Pence said. Without mentioning her by name, he pointed to the controversy surrounding Rep. Ilhan Omar, D-Minn., who has been rebuked by Republicans and Democrats for a series of remarks offensive to Jewish people.
"Anti-Semitism has no place in the Congress of the United States of America," he said. "Anyone who slanders those who support the historic alliance between the United States and Israel should never have a seat on the House Foreign Affairs Committee of the United States House of Representatives."
Pence's remarks follow weeks of Trump trying to persuade Americans that Jewish voters are leaving the Democratic Party in droves — a claim for which he has provided no evidence and which is at odds with larger trends in Jewish voting patterns away from Republicans and toward Democrats in recent elections.
Hallie Jackson asks Sanders: Does Trump truly believe that Dems hate Jewish people?
While the Democratic Party has struggled with opposition to Israel on its left flank, Trump has been accused of insensitivity to anti-Semitism in the past. Critics have pointed, in particular, to his conclusion that there were "very fine people on both sides" when white nationalists chanting "Jews will not replace us" clashed with protesters in Charlottesville, Virginia, in 2017 and the closing ad of his 2016 campaign, which featured the images of several prominent American Jews and anti-"globalist" rhetoric.
Pence’s remarks came as Trump welcomed Prime Minister Benjamin Netanyahu of Israel to the White House on Monday for meetings and to celebrate the signing of a presidential proclamation recognizing Israel’s long-disputed authority over the Golan Heights, going against decades of American foreign policy in the area.
“Israel has never had a better friend than you,” Netanyahu, who has battled corruption scandals and investigations of his own back home and faces a reelection fight in April, told Trump at the White House, touting a list of policy changes that the president has made since taking office.
The audience at AIPAC, too, has been pleased with Trump's policy toward Israel, which has mirrored the desires of many hard-liners. Trump officially moved the U.S. embassy in Israel to Jerusalem, pulled out of the Iran nuclear deal and recently announced that he would recognize Israel's claim on the contested Golan Heights region.
Lauren Egan and Eileen Street contributed.


An advantage of upgrading to Oracle 10g is that the cost-based optimizer (CBO) has been improved to choose the best execution plans based on statistics of the data. But one of the most common causes of performance issues in 10g databases is bad statistics. Luckily, 10g also introduces several extremely useful tools for monitoring database performance and activity including Active Workload Repository (AWR) and Automatic Database Diagnostic Monitor (ADDM) which can be used to pinpoint bad statistics.
One of the many advantages of upgrading to Oracle 10g is that the cost-based optimizer (CBO) has been improved to allow for better performance by using a cost model that accounts for I/O and CPU. This cost model allows the optimizer to choose the best execution plans based on statistics of the data. However, the decisions made by the CBO depend on the statistics that are available at the time that the execution plan is parsed. One of the most common causes of performance issues in 10g databases is bad statistics. Luckily, Oracle 10g also introduces several extremely useful tools for monitoring database performance and activity including Active Workload Repository (AWR) and Automatic Database Diagnostic Monitor (ADDM). These tools can be used to pinpoint where bad statistics might be causing the optimizer to make bad decisions.
The obvious question is, "What constitutes bad statistics?" Unfortunately, the answer is not as obvious as the question. In fact, unless you understand the nuts and bolts of how the CBO chooses its execution plan and how parsed execution plans are used in the library cache, it is unlikely that you will even know when bad statistics are causing your database to fail. The term "database failure" can have different meanings but what I am referring to is when CPU, I/O and wait times spike and stay elevated until the database is unusable, usually necessitating a database bounce.
I am going to discuss one case where a client required a root cause analysis for reoccurring database failures. Each time their database failed, they noticed the same symptoms -- suddenly the CPU, I/O and wait times spiked and stayed elevated. If the database failure occurred during production hours, the DBAs would bounce the database almost immediately and rely on Statspack reports to figure out what happened. But if the database failed outside normal business hours, the management rightfully insisted on a root cause determination prior to any corrective action. Since this client is a fairly large company, this meant that there would be a phone conference consisting of approximately 20 people trying to figure out what changed while the database was inaccessible for 6 to 18 hours. This team consisted of network administrators, database developers, DBAs, consultants and managers. I witnessed this happen numerous times in the few weeks I was at this client. The first time, the team decided to double the CPUs on the machine to combat the spiking CPU consumption. After this didn't solve the problem, the team of 20 determined that the corrective action was to create indexes and assign them to the keep pool. After the corrective action was taken and the database was restarted, the response times would become normal.
These intermittent failures were a top priority for this client since each failure had a substantial cost in resources and lost production time. Adding to the client's frustration, they had recently completed an engagement with a consulting company for performance tuning that same database.
My general approach to determining a root cause was similar to the client's approach. I wanted to find out what changed and then determine the cause for that change. Using the AWR to analyze the database CPU and I/O, I was able to pinpoint the exact snapshot where the sudden resource spike occurred.
Using the data above, it is obvious that something changed during snapshot 39244. The source of resource consumption on a segment can be ascertained by understanding all of the operations taking place in the database at a particular time. The next action in the diagnosis was to look at the SQL stats in AWR for the top SQL during the trouble snapshot. I focused on the major consumers identified in the top SQL of the Statspack report during the trouble period, verified by running an ADDM report. Starting with the greatest consumer, we see that the logical and physical read deltas had greatly increased while the executions remained fairly consistent.
This situation held true for each SQL statement in the top SQL. Furthermore, I noticed that the text of each of the top SQL had a similar predicate on the same table. Naturally, the next question was, "What caused the marginal cost of the same SQL query to increase exponentially?" This question can be answered by querying the AWR's SQL stats again for additional information.
Immediately, we notice that the sql plan hash value had changed. In other words, the execution plans for the same SQL has changed during the trouble snapshot. Comparing the two execution plans using AWR, I saw that the original plan used an efficient index (using an ID) while the new execution plan used a very inefficient plan (using a DATE).
The field CREATION_TS is a date field that shows the time that the record was first created. This particular table has several thousands of rows inserted daily. Why would the optimizer choose to range scan a time period with thousands of records to return one record, rather than using a selective index that only has one to three values? To any reasonable person viewing these two plans, it is obvious that the old plan is much more efficient. So what is causing the CBO to choose such a poor plan? Also, what is causing the execution plan to be reparsed causing the plans to change?
Since my objective was to determine the root cause for the database failure, my primary concern was the cause for the CBO using a poor execution plan. There are a number of reasons that the plan might be reparsed but an infrequent invalidation from the library cache should not cause a major problem. However, in our case, this invalidation was causing a new execution plan that was extremely inefficient leading to the failure of the database. Given this situation, I could easily have recommended using plan stability, but this would have been treating the symptom instead of curing the cause.
There are a few ways to determine the optimizer's cost-based decisions. Arguably, the most effective is a CBO trace. With this particular situation, the root problem was signified by more circumstantial data. Specifically, all of the TOP sql in the ADDM and Statspack reports during the trouble snapshot showed the exact same join on the same table within their SQL text. As shown above, the optimizer was driving decisions based on two predicates -- a date column and an ID column. For this table, there were only a few values for each ID while there are thousands of records for each date. The optimizer changed execution plans from using an index on the ID column to using an index on the DATE column.
Comparing the two plans, the cost for the plan using ID was being calculated equal to the cost using the DATE. However, after executing each plan, the session stats show that the plan using ID has only scanned 17 blocks while the plan using DATE had scanned over 38,000 blocks. Why is the cost for the poor plan being evaluated as lower than a much more efficient plan?
This client has an OLTP environment. Each of the queries that were identified as the top consumers were all querying for the most recent day's data. In other words, the value of the DATE range is between TRUNC(SYSDATE) and SYSDATE. Given all of this diagnostic data, my suspicion was that there was a column histogram on the DATE field causing the CBO to calculate costs based on old statistics. Sure enough, I was able to confirm that there was a height balanced column histogram on the DATE field.
With statistics being gathered weekly to biweekly, it was logical that the CBO believed the cost of using the most recent dates would be very low. In other words, when reparsing the SQL, the CBO believed that there were no values in the specified date range since the column histogram showed no values for that bucket. A CBO trace verified this situation and showed that the CBO calculated the cost for using that date range to be very low and chose the DATE index in the execution plan. In reality, this proved to be catastrophic to the database since this new plan consumed massive amounts of I/O and was executed many thousands of times per hour.
This situation was easy to demonstrate by using an old date range compared with a new date range. All queries using a date range prior to the date of the latest statistics formed execution plans using the index on the ID column while any date ranges after the latest statistics used the index on the DATE field. This demonstration showed that any plans using these predicates that were reparsed after the date of the latest statistics would favor using the index on the DATE field, resulting in very inefficient execution plans.
According to Oracle, it is only proper to use column histograms when the values of the column are highly skewed. Obviously a DATE field with a fairly consistent distribution of values does not fit this prescription. After asking the client's DBAs why they were gathering histograms for all indexed columns, they said that their developers had requested this option.
Finally, we had the root cause determination: the use of histograms on DATE fields in an OLTP database where the queries on this field were specifying the newest dates. This caused the CBO to miscalculate costs based on its belief that there was no data for the specified dates, hence resulting in fewer blocks to scan. The triggering event for the sudden degradation of performance was the reparsing of the SQL much after the date of the latest statistics. By removing the histogram on this column and reparsing the SQL, an immediate database-wide improvement and lasting stability was realized.
The really remarkable part about this root cause analysis is that the time of the analysis was completely independent from the date of the actual failure. In other words, Oracle 10g AWR and ADDM have made the once crucial need for analysis between crash and recovery a thing of the past. These tools are instrumental in analyzing database issues while allowing for the minimum downtime.
V.J. Jain is an Oracle Database and Applications consultant. With over 12 years of experience with database systems, he specializes in database performance, development, interfaces and high-performance solutions. Based in Orange County, California, he is active in exploring Oracle's newest technologies and is a member of the Oracle Partner Network and Beta program. Additional material by him can be found at Oracle-Developer.com.


Experience innovation in your workplace, firsthand.
See how the Job Tracking Template can help you be more productive by streamlining the management of tasks, staff, and clients associated with a job. You can learn to add more functionality with build-ons.
Assign jobs and tasks to staff.
Add and view job tasks.
Track time spent on a job.
Assign staff and clients to a job.
Manage task status and details.
Track time spent on tasks.
Whether it is staff, client, job or task management, start tracking them all with the Job Tracking Template.
Add more functionality with build-ons.
You can tailor the Job Tracking Template with additional features. To get started, download the template and follow the step-by-step build-on tutorials.
Gain visual insights into hours spent on and overall progress of jobs using FileMaker Charts.
Email invoices to customers that have billable time entries.
Enable iPad users to add file attachments to tasks using a mobile-friendly layout.
Allow iPad users to log time to the proper task and job using layouts optimized for their device.
Generate a report that shows job status and the amount of hours spent on each project.
Add support for multiple notes to track the progress of long-running tasks.
Quickly identify incomplete tasks that require attention summarized either by job or staff member.
Email task owners a list of action items that have an upcoming due date or that are overdue.
Watch an expert customize the Job Tracking Template using build-on features.
to customize apps with step-by-step tutorials.


I just want to record money that comes in and money that goes out. How do I do this?
The simplest way to record money that comes in is to use the "Deposit Book" facility.
The simplest way to record money that goes out is to use the "Cheque Book" facility.


Does Rihanna's Director Know Something About 'Diamonds' That We Don't?
'There's always multiple ways to look at the same situation,' Anthony Mandler says of Rihanna's new, dream-like clip.
By his best estimation, Anthony Mandler has made 16 videos with Rihanna — everything from early career pieces like 2006's "Unfaithful," high-profile, multi-artist collabos like "If I Never See Your Face Again" and "Run This Town" to dark, deeply-personal clips like "Russian Roulette" — but he'll be the first to tell you that he's never directed one like her latest, "Diamonds."
"I know that my journey with her has always been about exploring deep emotional narratives. But [videos like] 'Russian Roulette,' 'Disturbia,' 'Man Down,' 'Only Girl (In the World)' ... most of them take on a more linear journey," Mandler told MTV News. "With this one, I felt the need to create a wider landscape; almost hint at things, go into things, then get out of them, and not allow people to attach themselves to too much ... they needed to feel like dream vignettes, like, when you wake up from a dream, you realize what you were dreaming about is not really what it was about, it was about something else.
"This song and this album and who she is today, to me, it all feels like a new book; one book is over, and we're in a new book," he continued. "And in that new book, there's the idea of 'Let's try something different.' "
Go behind the wings of Rihanna's 777 Tour now!
And "Diamonds" is most definitely different ... it ditches a traditional narrative and stiches together a series of seemingly unrelated vignettes, and, in the process, paints a much larger portrait of Rihanna's much-discussed personal life. Which, in a way, is perhaps the most accurate portrayal to date.
"Nothing in life is black or white, just death and taxes, and there's always two sides to the story, and there's always multiple ways to look at the same situation, depending on who you are in that situation. Are you one of the people involved, or are you an outside viewer?" Mandler explained. "And you can see what I'm getting at in terms of relating this to Rihanna's real life, and what she's been through. What's truth or fiction? You know 'Is she drowning, or is she in complete ecstasy? Are those hands coming apart, or are they finding each other?' ... we tried to bring up these deeper questions that relate to song and her life and finding beauty in chaos and finding beauty in pain and finding pain in beauty."
Rihanna's willingness to trust Mandler's instincts is just one of the reasons why their partnership has produced so many iconic music videos ("Rihanna makes records that are attached to her and her journey. So we always feel like she's speaking to us from her heart," Mandler said. "And for me as a visual artist, you can't ask for anything more.") And though, in the week since "Diamonds" debuted, fans have worked overtime attempting to dissect each individual vignette — "Does the heavily tattooed arm she embraces belong Chris Brown?" is a particular point of contention — Mandler isn't about to divulge any secrets. After all, that debate is what he hoped to highlight in the first place. What is truth and what is fiction? Only he and Rihanna know for sure.
Rihanna hits the stage in Mexico City for her first 777 show.
"I'm obviously using what has been talked about and created, and truth and fiction and creating my own reality. Call that what you will," he said. "I'm hand-picking certain imagery in order to create impactful new imagery ... but I'm sworn to secrecy."


This disc in the series of live recordings from the Royal Festival Hall is almost the entire concert. Going on the length I would imagine the concerto is missing, possibly because the soloist did not give permission for the recording to be released. Instead we do have the encore. Like all the other discs from OCCD this is best judged as if one were an audience member on the night. Was it a good concert? Did you enjoy it? The answer to both those questions is "yes". From a record collectors point-of-view, this sequence of works could be reproduced at home drawing on separate sources for each piece. The questions then are different, and inevitably comparative. Is this as enjoyable as the other Egmont Overture recordings I own? Is the Brahms Symphony as impressive as, probably, Karajan or Klemperer? Does this recording sound as convincing as the best Decca sound of the period? And so on. The responses to those questions are not so positive. But, a big but, does one have to listen out for the 'best performance' all the time? I think not. As I have noted repeatedly in reviewing this series, what they offer is live concerts with all the atmosphere that entails. This is quite a different beast to a studio recording. Even back in the 60s studio recordings involved many takes and many edits so that the end result was effectively a patchwork.
Let me take the main work as an example, the Brahms. Ferencsik takes the work at a slightly faster pace than my library recordings, which I view as a benefit in this most trenchant of Brahms's four symphonic masterpieces. The orchestral recording is plenty clear enough to hear all the sections revving up the mighty Brahmsian engine and playing as if this music matters, not to gain technical perfection. Their sound is distinctive, the oboes have a reedy quality reminiscent of the Viennese oboe sound; the horns have a slight vibrato, a regular characteristic of Eastern European orchestras before the modern era; the timpanist cuts through the texture in the finale to exciting effect. It is often said that symphonies are a goal-led structure and Ferencsik has a clear aim so that when the coda ends the audience can only burst into applause. Perhaps I have heard more exciting Brahms Ones but that does not alter the feeling of satisfaction at reaching the goal here. None of these performances is "the best" but none can be described as less than good and I would love to have been there.
I always comment on the OCCD recording quality as being clear and alive in these simple and immediate twin-microphone recordings. Here the violins have a slightly acidic edge when at forte and above but the stereo picture is believable. The orchestra acquit themselves well. The audience obviously liked it at the time and a burst of enthusiastic applause follows each work to prove that. A short period of coughing helps the Beethoven get started as well. Once again Geoffrey Terry has achieved his aim to preserve live music making "for the record", as one might say. Without these efforts a lot of excellent performances would be only memories.


I ordered 3 swatches (Ivory, wheat, and natural) to decide which color runners I wanted for my wedding. I received them very quickly, and the swatches were HUGE too! Super helpful for getting a real feel for the material. I like the wheat color best, and I'm so excited to put my order in!!
I ordered 3 swatches to decide which color runners I wanted for my wedding. I received them very quickly, and I'm so excited to put my order in for the wheat colored runners! The swatches were HUGE too, which was helpful for getting a real feel for the material.


1. I used sox to split each input wave file into individual phonemes based on the forced alignment output. Then, I tried decoding each phoneme against its neighboring phonemes. The decoding output matched the expected phonemes only 12 out of 41 times for the exemplar recordings in the phrase "Approach the teaching of pronunciation with more confidence"
The accuracy for that method of edit distance scoring was 12/41 (29%) -- This naive approach didn't work well.
2. I used sox to split each input wave file into three phonemes based on the forced alignment output and position of the phoneme. If a phoneme is at beginning of its word, I used a grammar like: (current phone) (next) (next2next) and if it is middle phoneme: (previous) (current) (next) and if it is at the end: (previous2previous) (previous) (current) and supplied neighboring phones for the current phone and fixed the other two.
The accuracy was 19/41 (46.2%) -- better because of more contextual information.
The accuracy for this method of edit distance scoring was 30/41 (73.2%) -- the more contextual information provided, better the accuracy.
Here is some sample output, written both one below the other to have a comparison of phonemes.
In this case, both are forced outputs. So, if someone skips or inserts something during phrase recording, it may not work well. We need to think a method to solve this. Will a separate pass decoder grammar to test for whole word or syllable insertions and deletions work?
1. We are trying to combine acoustic standard scores (and duration) from forced alignment with an edit distance scoring grammar, which was reported to have better correspondence with human expert phonologists.
2. Complete a basic demo of the pronunciation evaluation without edit distance scoring from exemplar recordings using conversion of phoneme acoustic scores and durations to normally distributed scores, and then using those to derive their means and standard deviations, so we can produce per-phoneme acoustic and duration standard scores for new uploaded recordings.
3. Finalize the method for mispronunciation detection at phoneme and word level.
in order to test the new code's performance, tests similar to those in  and  where performed, with similar results in both resource utilization and it's ability to generate pronunciations for previously unseen words.
Having integrated the model training procedure into a simplified application, combined with the dictionary alignment code, the next step would be to create the evaluation code in order to avoid using phonetisaurus evaluate python script. Further steps include the writing of the necessary code to load the WFST binary model in java code, and convert it to the java's implementation of openFST , .
 Porting phonetisaurus many-to-many alignment python script to C++.
 Using OpenGrm NGram Library for the encoding of joint multigram language models as WFST.
 Porting openFST to java: Part 1.
 Porting openFST to java: Part 2.
2. I put some exemplar recordings for three phrases the project mentor had collected at http://talknicer.net/~ronanki/Datasets/ in each subdirectory there for each of the three phrases. The description of the phrases is at http://talknicer.net/~ronanki/Datasets/files/phrases.txt.
1. Write and test audio upload and pronunciation evaluation for per-phoneme standard scores.
If the phone is not as expected phoneme, check that phone in the list of neighboring phonemes of the expected phoneme.
d. Then, we can run sphinx3_align with this outcome against the same wav file to check whether the acoustic scores actually indicate a better match.
3. As an alternative to the above, I used sox to split each input wave file in to individual phoneme wav files using the forced alignment phone labels, and then used a separate recognition pass on each tiny speech segment. Now, I am writing separate grammar files for the neighboring phonemes for each phoneme. Once I complete them, I will check the output using decoder for each phoneme segment. This should provide for more accurate assessment of mispronunciations.
4. I will update the wiki here at https://cmusphinx.github.io/wiki/pronunciation_evaluation with my current tasks and milestones.
This article will review the OpenGrm NGram Library  and its usage for language modeling in ASR. OpenGrm makes use of functionality in the openFST library  to create, access and manipulate n-gram language models and it can be used as the language model training toolkit for integrating phonetisaurus' model training procedures  into a simplified application.
Next step is to count n-grams from an input corpus, converted in FAR format. It produces an n-gram model in the FST format. By using the switch --order the maximum length n-gram to count can be chosen.
The evaluation results above are, as expected, almost identical with those produced by the phonetisaurus' procedures and the use of MITLM toolkit instead of OpenGrm.
 I. H. Witten, T. C. Bell, "The zero-frequency problem: Estimating the probabilities of novel events in adaptive text compression", IEEE Transactions on Information Theory 37 (4), pp. 1085–1094, 1991.
 B. Carpenter, "Scaling high-order character language models to gigabytes", Proceedings of the ACL Workshop on Software, pp. 86–99, 2005.
 H. Ney, U. Essen, R. Kneser, "On structuring probabilistic dependences in stochastic language modeling", Computer Speech and Language 8, pp. 1–38, 1994.
 S. M. Katz, "Estimation of probabilities from sparse data for the language model component of a speech recogniser", IEEE Transactions on Acoustics, Speech, and Signal Processing 35 (3), pp. 400–401, 1987.
 R. Kneser, H. Ney, "Improved backing-off for m-gram language modeling", Proceedings of the IEEE International Conference on Acoustics, Speech, and Signal Processing (ICASSP). pp. 181–184, 1995.


"Here is what to do if you want to get a lift from a Vogon: forget it. They are one of the most unpleasant races in the Galaxy. Not actually evil, but bad-tempered, bureaucratic, officious and callous. They wouldn't even lift a finger to save their own grandmothers from the Ravenous Bugblatter Beast of Traal without orders - signed in triplicate, sent in, sent back, queried, lost, found, subjected to public inquiry, lost again, and finally buried in soft peat for three months and recycled as firelighters. The best way to get a drink out of a Vogon is to stick your finger down his throat, and the best way to irritate him is to feed his grandmother to the Ravenous Bugblatter Beast of Traal. On no account should you allow a Vogon to read poetry at you."
In the book, the vogons were responsible for Earth's destruction. The cause was simple: the planet was in the route of the new intergalactic autobahn. This is the typical vogon's way of life: too many races and several planets were destroyed to ease the intergalactic traffic.
Given two reference points that the new road must cross in a straight line and the coordinates and population of each planet in the spacial sector, write a program that generates a building report for the vogons.
The first line of the input contains the coordinates X1, Y1, X2, Y2 (-10.000 ≤ Xi, Yi ≤ 10.000) of the two reference points P1 and P2, separated by a single space. The coordinates are integers and the distance unit is the light-year.
The second line contains the number N (1 ≤ N ≤ 1.000) of the planets that belong to the spatial sector that the road crosses. The next N lines consist in the coordinates X and Y (-10.000 ≤ X, Y ≤ 10.000) and the number (in billions) of inhabitants H (1 ≤ H ≤ 100.000) of each planet. These values are integers separated by a single space.
The printed report has several lines. The first line contains the message "Relatorio Vogon #35987-2". The follow line must be the message "Distancia entre referencias: d anos-luz", where d is the distance between the two reference points, in light-years, with two decimal places.
In the next line must be printed the message "Setor Oeste:" and, in the next two lines, the messages "P planeta(s)" and "H bilhao(oes) de habitante(s)", where P is the number of the planets located in the left from the road (when traveled from first to second reference point) and H is the total of inhabitants from these planets. In the same way, must be printed three similar messages in reference to the "Setor Leste", the right side of the road.
Finally, must be printed, in the last line, the message "Casualidades: P planeta(s)", where P is the number of planets that were in the road line and, naturally, have to be destroyed by the vogons.