1 Chronicles 2 44

1 Chronicles 2:44 kjv

And Shema begat Raham, the father of Jorkoam: and Rekem begat Shammai.

1 Chronicles 2:44 nkjv

Shema begot Raham the father of Jorkoam, and Rekem begot Shammai.

1 Chronicles 2:44 niv

Shema was the father of Raham, and Raham the father of Jorkeam. Rekem was the father of Shammai.

1 Chronicles 2:44 esv

Shema fathered Raham, the father of Jorkeam; and Rekem fathered Shammai.

1 Chronicles 2:44 nlt

Shema was the father of Raham. Raham was the father of Jorkeam. Rekem was the father of Shammai.

1 Chronicles 2 verses

1 Chronicles 2 44 Meaning

This verse is part of the extensive genealogies within the Book of Chronicles, specifically detailing a lineage within the tribe of Judah through Caleb's descendants. It records Shema as the father of Raham, who was in turn the father of Jorkeam. The unique aspect of the verse is the concluding phrase, stating "and Jorkeam begot Raham" again. This repetition is unusual in biblical genealogies and has led to various scholarly interpretations, ranging from a textual variation (scribal error) to a deliberate literary device emphasizing a unique family occurrence or even referring to a different individual or place with the same name. Its primary meaning contributes to the overarching purpose of establishing Israel's lineage and heritage.

1 Chronicles 2 44 Context

1 Chronicles 2 begins the extensive genealogies that constitute a significant portion of the book. After covering the descendants of Adam and the patriarchs in Chapter 1, Chapter 2 focuses specifically on the tribe of Judah, Jacob's fourth son, emphasizing its central role in Israel's history and future kingship. The chapter meticulously lists the family lines of Judah, paying particular attention to Perez and Zerah, and then delves deeply into the descendants of Hezron, one of Judah's grandsons.

Verse 44 specifically appears within the genealogy of Caleb (son of Hezron), a prominent and righteous figure in Israelite history known for his faithfulness. The lines detailed here trace the lineage of Hur, Caleb's son, and highlight families who resided in Judah's territory. For the original audience, the post-exilic community returning to Jerusalem, these genealogies were crucial for reaffirming their tribal identity, validating land ownership claims, legitimizing priestly and Levitical service, and connecting them to their glorious past and the covenant promises made to their ancestors, particularly the line of David. The meticulous nature of these records served as a powerful reminder of God's enduring faithfulness to His people, ensuring their identity was not lost despite the displacement and disruption of exile. The listing of specific individuals, even less prominent ones, contributes to the unbroken chain of continuity and identity.

1 Chronicles 2 44 Word analysis

• And Shema: (Hebrew: שֶׁמַע, Shema) - This name means "hearing" or "fame." Shema is listed here as a descendant in the lineage of Judah, through Caleb and Hur. His inclusion reinforces the detailed nature of the Chronicler's record-keeping for every branch of the leading tribe.
• begot: (Hebrew: יָלַד, yalad) - This verb is consistently used in biblical genealogies to denote biological paternity or to establish a line of descent. Its repeated use highlights direct generational continuity, emphasizing a direct ancestral link rather than a metaphorical or adopted one.
• Raham: (Hebrew: רַחַם, Racham) - This name can mean "compassion" or "womb." Raham is recorded here as the son of Shema. The subsequent repetition of his name is the most striking feature of this verse.
• the father of: (Hebrew: אֲבִי, ’avi) - A possessive form of 'father', explicitly stating the paternal relationship and identifying the direct progenitor.
• Jorkeam: (Hebrew: יָרְקְעָם, Yorqe'am) - This name is less common and might relate to a concept like "people will be stretched out." Jorkeam is identified as the son of Raham.
• and Jorkeam begot Raham: This exact repetition of "begot Raham" is a textual peculiarity. In the Masoretic Text (the standard Hebrew Bible), the second "Raham" is identical to the first. Scholars generally view this as:
  • Scribal Error (Dittography): The most common scholarly explanation is that a scribe inadvertently copied the name "Raham" twice due to repetition in the previous clause or proximity of similar words, or due to a haplography (omission of one of two identical successive words/letters) in an earlier manuscript being overcorrected.
  • Rare Naming Convention: Less likely, it could indicate a rare instance where Jorkeam indeed had a son named Raham, carrying the same name as his own father (Shema's son). While possible, it's highly unusual for genealogies to emphasize this specific repetition without further clarification.
  • Reference to a Clan or Place: Some suggest "Raham" might also refer to a clan, a family branch, or even a location associated with this lineage, rather than a second distinct individual named Raham. However, the use of "begot" ("yalad") usually refers to individuals.
  Regardless, the presence of such a detail, even if a scribal variant, does not undermine the overall accuracy or divine inspiration of the Scriptures, but rather provides insight into the meticulous yet human process of textual transmission throughout history. It further emphasizes the Chronicler's commitment to record details.

• "Shema begot Raham, the father of Jorkoam": This phrase adheres to the standard formula for conveying patriarchal lineage. It clearly establishes a direct, three-generation succession within a specific branch of the Calebite line, providing granular detail about family relationships vital for understanding the complex tribal structures.
• "and Jorkoam begot Raham": The striking recurrence of "begot Raham" after Raham was already introduced as Jorkeam's father signifies the textual anomaly. This specific word group prompts inquiry into the exact reading and the ancient transmission of biblical texts. While potentially a copyist's error, its retention in the Masoretic Text highlights the meticulous and often conservative approach to preserving the scriptural text as it was found. For the Chronicler, the accuracy of recording names, however small or repetitive, was paramount in reconnecting a scattered people to their heritage and promise.

1 Chronicles 2 44 Bonus section

• The Chronicler's emphasis on comprehensive genealogies reflects the Israelite worldview where one's identity, tribal affiliation, inheritance, and place in the covenant community were intrinsically tied to ancestry. For the returning exiles, these lists provided tangible proof of their claim to the land and their identity as God's chosen people.
• While the specific reason for the textual repetition of "Raham" is not definitively known, such nuances demonstrate the meticulousness with which the Hebrew scriptures were transmitted over centuries. Every effort was made to copy the text as accurately as possible, and sometimes, even perceived errors or unusual structures were faithfully reproduced rather than "corrected" without certain knowledge of the original intent.
• This verse, along with others detailing lesser-known lineages, forms a vital part of the larger genealogical fabric that ultimately leads to the line of David, highlighting God's faithfulness in preparing the way for the coming Messiah through an unbroken, meticulously recorded lineage.

1 Chronicles 2 44 Commentary

1 Chronicles 2:44, embedded within the extensive genealogies of Judah, primarily functions to solidify the meticulous historical record that connects the post-exilic community to their ancestral heritage. While the specific individuals — Shema, Raham, and Jorkeam — are not prominent figures mentioned elsewhere in grand narratives, their inclusion validates the unbroken chain of generations descending from Judah and Caleb, a linage crucial for land rights, social standing, and ultimately, the future Messianic hope.

The textual peculiarity of "Jorkeam begot Raham" following "Shema begot Raham, the father of Jorkoam" has long engaged biblical scholars. Rather than undermining the divine authority of Scripture, this specific instance sheds light on the nature of ancient text transmission, acknowledging the human element in the meticulous copying process. It reminds us that God sovereignly oversaw the preservation of His Word, even allowing for minor textual variations while safeguarding the core message and theological truth. The Chronicler's overall goal was to present a continuous, accurate (from their perspective and available records) historical record to encourage and legitimize the identity of the returning exiles. This seemingly minor verse thus contributes to the grand narrative of God's covenant faithfulness extended across generations, demonstrating His commitment to His people's identity and future.